> ## Documentation Index > Fetch the complete documentation index at: https://docs.intentleads.si/llms.txt > Use this file to discover all available pages before exploring further. # Remove a keyword > Removes a keyword from a lane, matched on its exact text (case-insensitive). Checks and exports stop using it straight away; the lane's counts update at its next check. **Free.** This doesn't use any contacts from your plan. ## OpenAPI ````yaml /api-reference/openapi.json delete /api/v1/lanes/{code}/keywords openapi: 3.1.0 info: title: Intent Leads API version: '1.0' description: >- The Intent Leads API finds B2B people actively researching the topics you sell into, and exports them with contact details into your own tools. **Authentication.** Send an API key as a bearer token: `Authorization: Bearer il_live_…`. Keys belong to one organization. Standard keys work with everything except billing, team and key management, which need an admin key. **What costs contacts.** Only `POST /api/v1/exports` with `"dry_run": false` uses contacts from your plan. Quotes, counts, checks, samples and re-downloads are free. **Errors.** Every error is JSON: `{"error": "code", "message": "Plain-English explanation"}`. Codes are stable; messages may change. **Conventions.** JSON by default. Dates are `YYYY-MM-DD` and timestamps ISO 8601, all in UTC. Lane codes (`L1`) are case-insensitive. servers: - url: https://intentleads.si security: - bearerAuth: [] tags: - name: Exports description: Quote (free) and buy new people from your lanes, then download them. - name: Leads description: Pull and re-download the leads you've exported, and list deliveries. - name: Lanes description: >- Create, inspect and tune lanes: keywords plus the companies and roles you want. - name: Keywords description: Add and remove a lane's keywords; each one is approved as its own topic. - name: Checks description: >- Free lane checks that size every filter step over 14 days, plus quick topic signals. - name: Company list description: >- The target-company list your lanes can narrow to or use instead of industries. - name: Suppressions description: People you exported who later asked to be removed. - name: Usage description: Contacts used and left this billing period. - name: Billing description: Plan, invoices and plan changes. Admin keys only. - name: Team description: Members and invite links. Admin keys only. - name: API keys description: Create, rename, rotate and revoke API keys. Admin keys only. - name: Account description: Check which organization a key belongs to and its role. - name: Reference description: Valid values for lane filters. - name: Activity description: A feed of changes and events in your organization. paths: /api/v1/lanes/{code}/keywords: delete: tags: - Keywords summary: Remove a keyword description: >- Removes a keyword from a lane, matched on its exact text (case-insensitive). Checks and exports stop using it straight away; the lane's counts update at its next check. **Free.** This doesn't use any contacts from your plan. operationId: removeKeyword parameters: - $ref: '#/components/parameters/LaneCode' - name: keyword in: query required: true description: The keyword to remove, exact text (case-insensitive). schema: type: string example: finding medical device distributors responses: '200': description: Keyword removed. content: application/json: schema: type: object properties: lane: type: string removed: type: string description: The keyword as it was stored. required: - lane - removed example: lane: L1 removed: finding medical device distributors '400': description: No keyword given, or it couldn't be removed. content: application/json: schema: $ref: '#/components/schemas/Error' examples: keyword_required: value: error: keyword_required message: Pass ?keyword=… to remove. invalid_keyword: value: error: invalid_keyword message: Couldn't remove the keyword. Try again. '401': $ref: '#/components/responses/Unauthorized' '404': description: No such lane, or the keyword isn't in it. content: application/json: schema: $ref: '#/components/schemas/Error' examples: lane_not_found: value: error: lane_not_found message: No lane L9. keyword_not_found: value: error: keyword_not_found message: That keyword isn't in this lane. '500': $ref: '#/components/responses/InternalError' components: parameters: LaneCode: name: code in: path required: true description: Lane code, e.g. `L1`. Case-insensitive. schema: type: string example: L1 schemas: Error: type: object properties: error: type: string example: lane_not_found description: Stable machine-readable code, e.g. `lane_not_found`. message: type: string example: No lane L9. description: Plain-English explanation you can show to a person. required: - error - message description: Every error has this shape. responses: Unauthorized: description: Missing, malformed, unknown or revoked API key. content: application/json: schema: $ref: '#/components/schemas/Error' examples: unauthorized: value: error: unauthorized message: 'Send a valid API key as: Authorization: Bearer il_live_…' InternalError: description: >- Unexpected server error. Safe to retry reads; retry an export only with the same `idempotency_key`. content: application/json: schema: $ref: '#/components/schemas/Error' examples: internal_error: value: error: internal_error message: Something went wrong. Try again. securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: il_live_… description: >- An Intent Leads API key, e.g. `il_live_` followed by 32 letters and digits. Create one on the API and CLI page of the dashboard. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.