> ## 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 audience API

> Detail for one audience including its definition, member count, build status and crawl cadence. Free.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="How do I know how stale an audience is?">
    `membership_at` is when the membership was last built. For a computed audience that is a snapshot date — re-`PATCH` the definition to refresh it. Separately, [the technology report](/docs/api-reference/audiences/audience-technologies-api) returns a `freshness` block describing how recently the *detection data* about those domains was refreshed, which is a different question.
  </Accordion>

  <Accordion title="Why is my audience id returning 404?">
    Audiences are owned per API key. Ids belonging to another key return 404 rather than 403, so they cannot be probed.
  </Accordion>
</AccordionGroup>


## OpenAPI

````yaml GET /v1/segments/{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/segments/{id}:
    get:
      tags:
        - Audiences
      summary: Get audience API
      description: >-
        Detail for one audience, including its definition, member count, build
        status and crawl cadence. Another key's audience id returns 404. Free.
      operationId: getAudience
      parameters:
        - name: id
          in: path
          required: true
          description: The audience id.
          schema:
            type: string
            example: seg_8f3a2c1b
      responses:
        '200':
          description: Audience detail
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  data:
                    type: object
                    properties:
                      segment:
                        $ref: '#/components/schemas/Audience'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '404':
          $ref: '#/components/responses/NotFound'
        '429':
          $ref: '#/components/responses/RateLimited'
components:
  schemas:
    Audience:
      type: object
      properties:
        id:
          type: string
          example: seg_8f3a2c1b
        name:
          type: string
          example: YC W25 portfolio
        type:
          type: string
          enum:
            - filter
            - list
          description: >-
            `list` for an uploaded set of domains, `filter` for a computed
            recipe. Immutable.
          example: list
        kind:
          type: string
          enum:
            - upload
            - firmo
            - technology
            - signal
          description: >-
            How membership was produced. `upload` is a pasted list; the rest are
            computed recipes.
          example: upload
        definition:
          type: object
          nullable: true
          description: The recipe that produced membership. `null`-ish for uploads.
        domain_count:
          type: integer
          description: Members in the current generation.
          example: 5914
        status:
          type: string
          enum:
            - uploading
            - ready
            - failed
          example: ready
        membership_at:
          type: string
          nullable: true
          description: >-
            When membership was last built. Computed audiences are point-in-time
            snapshots — re-send the definition to refresh.
          example: '2026-07-29T10:14:02.000Z'
        matched_total:
          type: integer
          nullable: true
        crawl_cadence:
          type: string
          enum:
            - none
            - weekly
            - daily
          default: none
          example: none
        last_dispatched_at:
          type: string
          nullable: true
        created_at:
          type: string
          example: '2026-07-29T10:12:00.000Z'
        updated_at:
          type: string
          example: '2026-07-29T10:14:02.000Z'
    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)

````