> ## 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. # List suppressions > People you exported who later asked to be removed. Under the data terms, delete them from your own systems (CRM, sequencer, spreadsheets) within 10 business days of `suppressed_at`. Match on `lead_id`, or on `email_sha256`: the SHA-256 (hex) of the trimmed, lowercased email the person was recorded under. That can be a different address from the lead's `business_email`, so prefer `lead_id`. Oldest first, up to 10,000. Use `since` to fetch only new ones. Suppressed people also come back with `suppressed: true` and empty contact fields in every re-download, and are left out of all future exports. **Free.** This doesn't use any contacts from your plan. ## OpenAPI ````yaml /api-reference/openapi.json get /api/v1/suppressions 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/suppressions: get: tags: - Suppressions summary: List suppressions description: >- People you exported who later asked to be removed. Under the data terms, delete them from your own systems (CRM, sequencer, spreadsheets) within 10 business days of `suppressed_at`. Match on `lead_id`, or on `email_sha256`: the SHA-256 (hex) of the trimmed, lowercased email the person was recorded under. That can be a different address from the lead's `business_email`, so prefer `lead_id`. Oldest first, up to 10,000. Use `since` to fetch only new ones. Suppressed people also come back with `suppressed: true` and empty contact fields in every re-download, and are left out of all future exports. **Free.** This doesn't use any contacts from your plan. operationId: listSuppressions parameters: - name: since in: query required: false description: Only suppressions on or after this date (`YYYY-MM-DD`, UTC). schema: type: string format: date example: '2026-10-01' responses: '200': description: Suppressed leads. content: application/json: schema: type: object properties: since: type: - string - 'null' format: date description: The `since` you sent, or null. suppressions: type: array items: $ref: '#/components/schemas/Suppression' note: type: string required: - since - suppressions - note example: since: '2026-10-01' suppressions: - lead_id: 0199e3b2-5a7c-7e21-b4d3-8c9f0a1b2c3e email_sha256: >- 5f2b9c7a1e4d8f6b3a0c9e2d7b5f1a8c4e6d2b9f7a3c5e1d8b6f4a2c0e9d7b5f suppressed_at: '2026-10-09T11:20:00.000000+00:00' note: >- Delete these people from your systems within 10 business days of suppressed_at. '400': description: '`since` isn''t a date.' content: application/json: schema: $ref: '#/components/schemas/Error' examples: invalid_since: value: error: invalid_since message: since must be a date like 2026-10-01. '401': $ref: '#/components/responses/Unauthorized' '500': $ref: '#/components/responses/InternalError' components: schemas: Suppression: type: object properties: lead_id: type: string format: uuid email_sha256: type: - string - 'null' pattern: ^[0-9a-f]{64}$ description: >- SHA-256 (hex) of the trimmed, lowercased email the person was recorded under. Null when there was none. This can be a different address from `business_email`, so match on `lead_id` first. suppressed_at: type: string format: date-time required: - lead_id - email_sha256 - suppressed_at 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.