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

# Export lead list API

> Download a finished list as CSV or newline-delimited JSON with technology names resolved and contact columns attached. Free.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does exporting cost credits?">
    No. You paid per row when the list was built, so downloading it is free and you can export the same list as often as you like until it expires.
  </Accordion>

  <Accordion title="What contact data is included?">
    Every export carries `emails` and `phones` (semicolon-joined when there are several) plus five social profile URLs — LinkedIn, X, Facebook, Instagram and YouTube — reconstructed from handles found during the crawl. Domains on the enrichment opt-out list export empty contact fields with the rest of the row intact.
  </Accordion>

  <Accordion title="Which format should I pick?">
    `csv` for spreadsheets and most CRM importers. `json` returns newline-delimited JSON, one object per line, which streams well into data pipelines without loading the whole file into memory.
  </Accordion>

  <Accordion title="How large can an export be?">
    Up to 100,000 rows. The response streams directly from the database, so large exports do not time out.
  </Accordion>
</AccordionGroup>


## OpenAPI

````yaml GET /v1/leads/lists/{id}/export
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}/export:
    get:
      tags:
        - Lead lists
      summary: Export lead list API
      description: >-
        Download a finished list as CSV or newline-delimited JSON, with
        technology names resolved from ids. The response streams straight from
        the database and supports lists up to 100,000 rows.


        Every export carries the contact columns — `emails`, `phones` and five
        social profile URLs reconstructed from handles found during the crawl.
        Free: you already paid per row when the list was built.
      operationId: exportLeadList
      parameters:
        - name: id
          in: path
          required: true
          description: The lead list id.
          schema:
            type: string
            format: uuid
            example: f6ab2d94-c34f-47b7-9d1a-228e71488cd2
        - name: format
          in: query
          required: true
          description: Output format.
          schema:
            type: string
            enum:
              - csv
              - json
            example: csv
      responses:
        '200':
          description: The list as a downloadable file
          headers:
            Content-Disposition:
              description: '`attachment` with a generated filename.'
              schema:
                type: string
          content:
            text/csv:
              schema:
                type: string
                format: binary
              example: >-
                "domain","detection_url","technologies","company_name","emails","phones","social_linkedin"

                "example.com","EXAMPLE.COM","Cloudflare","Example
                Corp","hi@example.com","+1 555
                0100","https://www.linkedin.com/company/example"
            application/json:
              schema:
                type: string
                format: binary
              example: >-
                {"domain":"example.com","technologies":"Cloudflare","company_name":"Example
                Corp"}

                {"domain":"acme.com","technologies":"Cloudflare,
                WordPress","company_name":"Acme"}
        '400':
          $ref: '#/components/responses/BadRequest'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '429':
          $ref: '#/components/responses/RateLimited'
components:
  responses:
    BadRequest:
      description: Invalid or missing parameters
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/ApiError'
          example:
            success: false
            error:
              code: VALIDATION_ERROR
              message: >-
                Provide exactly one scope: technology_id, technology or
                category_id.
    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'
  schemas:
    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
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      description: >-
        API key in format `tapi_live_[32-char]` (live) or `tapi_test_[32-char]`
        (test)

````