> ## 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.

# Get lead list API

> Detail for one lead list including its full filter set, row counts, credits charged and preview/download flags. Free.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="How do I know when my list is finished?">
    Poll this endpoint until `status` is `ready`. At that point `actual_count` holds the real row count, `credits_charged` holds what you paid, and `can_preview` and `can_download` both flip to `true`.
  </Accordion>

  <Accordion title="Why is actual_count lower than estimated_count?">
    The estimate is a fast approximation; the actual count is what the query really matched. You are charged on the actual count, so a lower number costs you less.
  </Accordion>

  <Accordion title="What are can_preview and can_download for?">
    They save you from encoding status rules on your side. Both are `true` only when the list is `ready` — `processing`, `failed` and `expired` all yield `false`.
  </Accordion>
</AccordionGroup>


## OpenAPI

````yaml GET /v1/leads/lists/{id}
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/{id}:
    get:
      tags:
        - Lead lists
      summary: Get lead list API
      description: >-
        Detail for one lead list including its full filter set, row counts,
        credits charged and the `can_preview` / `can_download` flags. Poll this
        after `POST /v1/leads/create` until `status` is `ready`. Free.
      operationId: getLeadList
      parameters:
        - name: id
          in: path
          required: true
          description: The lead list id.
          schema:
            type: string
            format: uuid
            example: f6ab2d94-c34f-47b7-9d1a-228e71488cd2
      responses:
        '200':
          description: Lead list detail
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  data:
                    $ref: '#/components/schemas/LeadList'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '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'
    NotFound:
      description: Resource not found
      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)

````