> ## 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 deliveries > Each export writes one delivery per lane it filled. Returns the latest 200, newest first. Get one delivery's leads with `GET /api/v1/leads?since=YYYY-MM-DD&delivery=ID`, using a `since` on or before its `delivered_on`. **Free.** This doesn't use any contacts from your plan. ## OpenAPI ````yaml /api-reference/openapi.json get /api/v1/deliveries 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/deliveries: get: tags: - Leads summary: List deliveries description: >- Each export writes one delivery per lane it filled. Returns the latest 200, newest first. Get one delivery's leads with `GET /api/v1/leads?since=YYYY-MM-DD&delivery=ID`, using a `since` on or before its `delivered_on`. **Free.** This doesn't use any contacts from your plan. operationId: listDeliveries responses: '200': description: Deliveries, newest first. content: application/json: schema: type: object properties: deliveries: type: array items: $ref: '#/components/schemas/Delivery' required: - deliveries example: deliveries: - id: 413 delivered_on: '2026-10-14' lane: L2 people: 61 contacts_billed: 61 - id: 412 delivered_on: '2026-10-14' lane: L1 people: 189 contacts_billed: 189 '401': $ref: '#/components/responses/Unauthorized' '500': $ref: '#/components/responses/InternalError' components: schemas: Delivery: type: object properties: id: type: integer description: >- Delivery id. Filter leads with `GET /api/v1/leads?since=DATE&delivery=ID`. delivered_on: type: string format: date description: UTC date the delivery was written. lane: type: - string - 'null' description: Lane code, or null if that lane no longer exists. people: type: integer description: People in this delivery. contacts_billed: type: integer description: Contacts this delivery used from your plan. required: - id - delivered_on - lane - people - contacts_billed description: Each export writes one delivery per lane it filled. 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.