> ## Documentation Index > Fetch the complete documentation index at: https://technologychecker.io/docs/llms.txt > Use this file to discover all available pages before exploring further. # List lead lists API > Every lead list on your API key with status, row counts, credits charged and a filter summary. Free. ## Frequently asked questions `processing` — the background job is still running. `ready` — rows are available to preview and export. `failed` — the job errored and nothing was charged. `expired` — the list passed its 60-day retention and its rows were deleted. No, the rows are gone. The list metadata including its filters is retained, so you can rebuild it with the same criteria — that costs credits again, and results will reflect current data. ## OpenAPI ````yaml GET /v1/leads/lists openapi: 3.1.0 info: title: TechnologyChecker API description: >- Discover technology stacks, track market trends, and enrich data with company intelligence. version: 1.0.0 contact: name: TechnologyChecker Support email: support@technologychecker.io url: https://technologychecker.io servers: - url: https://api.technologychecker.io description: Production security: - bearerAuth: [] tags: - name: Domain technologies description: Look up technologies detected on any domain - name: Technology data description: Search, look up, and get details on tracked technologies - name: Market intelligence description: Technology stats, trends, and market share - name: Company data description: Firmographic and company intelligence - name: Live detection description: Real-time technology detection with browser rendering - name: Signals description: >- Intent signals derived from technology state transitions: who adopted, who churned, who switched, and who has a gap in their stack. - name: Alerts description: >- Saved signal queries delivered to your webhook. Every signal you can query, you can subscribe to. - name: Audiences description: >- Saved groups of domains — uploaded lists or computed recipes — that you can profile, slice and monitor. - name: Lead lists description: >- Build and export targeted domain lists combining technology detection with company data. paths: /v1/leads/lists: get: tags: - Lead lists summary: List lead lists API description: >- Every lead list owned by the calling API key, with status and a filter summary. Free. operationId: listLeadLists parameters: - name: status in: query required: false description: Filter by status. schema: type: string enum: - processing - ready - failed - expired - name: limit in: query required: false description: Results per page. Capped at 100. schema: type: integer default: 20 maximum: 100 - name: offset in: query required: false description: Pagination offset. schema: type: integer default: 0 responses: '200': description: Your lead lists content: application/json: schema: type: object properties: success: type: boolean example: true data: type: object properties: lists: type: array items: $ref: '#/components/schemas/LeadList' total: type: integer example: 1 limit: type: integer example: 20 offset: type: integer example: 0 '401': $ref: '#/components/responses/Unauthorized' '429': $ref: '#/components/responses/RateLimited' components: schemas: LeadList: type: object properties: id: type: string format: uuid example: f6ab2d94-c34f-47b7-9d1a-228e71488cd2 name: type: string example: US SaaS Companies status: type: string enum: - processing - ready - failed - expired example: ready estimated_count: type: integer example: 1000 actual_count: type: integer example: 1000 credits_charged: type: integer example: 1000 created_at: type: string example: '2026-01-15 19:19:19' completed_at: type: string nullable: true example: '2026-01-15 19:19:49' expires_at: type: string description: Results are deleted 60 days after creation. example: '2026-03-16T19:19:19.875Z' filters: $ref: '#/components/schemas/LeadListFilters' can_preview: type: boolean example: true can_download: type: boolean example: true LeadListFilters: type: object description: >- The filter set that defines a lead list. Technology filters and company filters combine with AND. properties: technologies: type: object properties: ids: type: array items: type: integer example: - 2 - 7 logic: type: string enum: - or - and - and_not default: or description: >- `or` matches domains running any listed technology. `and` requires all of them. `and_not` requires the first and excludes the rest. keywords: type: object properties: include: type: array items: type: string example: - shop exclude: type: array items: type: string example: - health website_type: type: string example: company_only countries: type: array items: type: string example: - United States - Germany industries: type: array items: type: string example: - Software Development employees: type: array items: type: string example: - 51-200 - 201-500 has_email: type: boolean description: Only domains where the crawler found an email address. has_phone: type: boolean description: Only domains where the crawler found a phone number. languages: type: array items: type: string example: - en web_countries: type: array items: type: string description: >- ISO-2 codes or English names. Unresolvable values are rejected at create time. example: - USA ApiError: type: object properties: success: type: boolean example: false error: type: object properties: code: type: string example: UNAUTHORIZED message: type: string example: Missing or invalid API key responses: Unauthorized: description: Missing or invalid API key content: application/json: schema: $ref: '#/components/schemas/ApiError' RateLimited: description: Rate limit exceeded content: application/json: schema: $ref: '#/components/schemas/ApiError' securitySchemes: bearerAuth: type: http scheme: bearer description: >- API key in format `tapi_live_[32-char]` (live) or `tapi_test_[32-char]` (test) ````