> ## Documentation Index
> Fetch the complete documentation index at: https://api.tryspecter.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Find company ID

> Resolve a batch of alternate identifiers (domain, website, LinkedIn URL, or company name) into the Specter company `id`. Re-use that `id` with the id-only company endpoints such as [Get company by ID](/api-reference/companies/get-company-by-id).

<Note> This endpoint is free; resolving identifiers to IDs uses no credits. The id-only endpoints you call next are charged as usual. </Note>

## What you need

One or more identifiers to resolve: a domain, website, LinkedIn URL, or company name (1–50 per request). No Specter ID is required; that is what this returns.

## Behaviour

- Pass identifiers under `to_resolve` (1-50 per request). Each entry must carry exactly one identifier; none, or more than one, returns a validation error.
- The response has one result group per input, in the same order, so you can attribute each set of matches back to what you sent. `query` echoes the normalized identifier.
- `domain` matches the primary domain and any domain aliases; `website_url` is reduced to its domain before matching.
- Exact identifiers (`domain`, `website_url`, `linkedin_url`) return at most one company, with `match_confidence` `1`.
- `name` is fuzzy-matched and can return several ranked candidates (at most 10). Each carries a `match_confidence` from 0 to 1, relative to the other results for that query; use the extra fields (domain, HQ, founded year) to pick the right one.
- An identifier that matches nothing keeps its place with an empty `matches` list.

## What you do next

- **Get the full profile.** Pass the returned `company_id` to [Get company by ID](/api-reference/companies/get-company-by-id).
- **See who it competes with.** Feed the `company_id` to [Get company competitors](/api-reference/companies/get-company-competitors).
- **Track its news.** Pull [Get company news](/api-reference/companies/get-company-news) for the resolved company.




## OpenAPI

````yaml /api-ref/bundle_api.yaml post /companies/resolve
openapi: 3.0.0
info:
  title: Specter API
  termsOfService: https://tryspecter.com/terms/
  contact:
    name: API support
    email: api-support@tryspecter.com
  version: 1.0.0
servers:
  - description: Production
    url: https://app.tryspecter.com/api/v1
security:
  - ApiKeyAuth: []
tags:
  - name: Enrich
    description: >
      Look up a company, person, or investor and, if Specter does not already
      hold it, fetch it on demand. Includes email-based person enrichment.
  - name: Search
    description: |
      Find records across every product from a single plain-English query.
  - name: Companies
    description: >
      Company profiles, funding, headcount, traction, the per-company signals
      and sub-resources attached to a single company, and identifier resolution.
  - name: People
    description: >
      Specter people records: profile data, contact details, and per-person
      lookups for a known person ID.
  - name: Investors
    description: >
      Specter investor records: profile, activity, targeting, funds, portfolio
      companies, and the funding rounds they have participated in.
  - name: Transactions
    description: |
      Transaction detail by ID: funding rounds, acquisitions, and IPOs.
  - name: News Signals
    description: |
      Company-level news signals: by ID, and for a saved list or company search.
  - name: Revenue Signals
    description: >
      Revenue and profitability signals: by ID, by date, and for a saved list or
      company search.
  - name: Talent Signals
    description: |
      Talent signals: by ID and in bulk by ID.
  - name: Investor Interest Signals
    description: |
      Investor interest signals: by ID and in bulk by ID.
  - name: Company Lists
    description: |
      Create, query, and maintain lists of companies, including their results.
  - name: Investor Lists
    description: |
      Create, query, and maintain lists of investors, including their results.
  - name: People Lists
    description: |
      Create, query, and maintain lists of people, including their results.
  - name: Saved Searches
    description: |
      List and delete searches saved via tryspecter.com.
  - name: Company Saved Searches
    description: |
      Details and results for saved company searches.
  - name: People Saved Searches
    description: |
      Details and results for saved people searches.
  - name: Investor Saved Searches
    description: |
      Details and results for saved investor searches.
  - name: Talent Signals Saved Searches
    description: |
      Details and results for saved Talent Signals searches.
  - name: Investor Interest Saved Searches
    description: |
      Details and results for saved Investor Interest Signals searches.
  - name: Network
    description: >
      Your team's LinkedIn network: the people and companies your teammates are
      connected to, and your reach into a given company.
  - name: Account
    description: >
      Organisation-level resources: your team's members, API call logs, and
      credit balance.
paths:
  /companies/resolve:
    post:
      tags:
        - Companies
      summary: Find company ID
      description: >
        Resolve a batch of alternate identifiers (domain, website, LinkedIn URL,
        or company name) into the Specter company `id`. Re-use that `id` with
        the id-only company endpoints such as [Get company by
        ID](/api-reference/companies/get-company-by-id).


        <Note> This endpoint is free; resolving identifiers to IDs uses no
        credits. The id-only endpoints you call next are charged as usual.
        </Note>


        ## What you need


        One or more identifiers to resolve: a domain, website, LinkedIn URL, or
        company name (1–50 per request). No Specter ID is required; that is what
        this returns.


        ## Behaviour


        - Pass identifiers under `to_resolve` (1-50 per request). Each entry
        must carry exactly one identifier; none, or more than one, returns a
        validation error.

        - The response has one result group per input, in the same order, so you
        can attribute each set of matches back to what you sent. `query` echoes
        the normalized identifier.

        - `domain` matches the primary domain and any domain aliases;
        `website_url` is reduced to its domain before matching.

        - Exact identifiers (`domain`, `website_url`, `linkedin_url`) return at
        most one company, with `match_confidence` `1`.

        - `name` is fuzzy-matched and can return several ranked candidates (at
        most 10). Each carries a `match_confidence` from 0 to 1, relative to the
        other results for that query; use the extra fields (domain, HQ, founded
        year) to pick the right one.

        - An identifier that matches nothing keeps its place with an empty
        `matches` list.


        ## What you do next


        - **Get the full profile.** Pass the returned `company_id` to [Get
        company by ID](/api-reference/companies/get-company-by-id).

        - **See who it competes with.** Feed the `company_id` to [Get company
        competitors](/api-reference/companies/get-company-competitors).

        - **Track its news.** Pull [Get company
        news](/api-reference/companies/get-company-news) for the resolved
        company.
      requestBody:
        description: The identifiers to resolve.
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                to_resolve:
                  type: array
                  minItems: 1
                  maxItems: 50
                  items:
                    $ref: '#/components/schemas/CompanyResolveIdentifier'
              required:
                - to_resolve
              additionalProperties: false
            example:
              to_resolve:
                - domain: stripe.com
                - name: Stripe
      responses:
        '200':
          $ref: '#/components/responses/CompanyResolveResponse'
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
        '422':
          description: >
            `to_resolve` is missing or empty, or an item provides no identifier,
            more than one, or a malformed value (e.g. a `name` shorter than 3
            characters).
        '429':
          $ref: '#/components/responses/RateLimits'
components:
  schemas:
    CompanyResolveIdentifier:
      type: object
      description: >
        One alternate company identifier. Supply exactly one of the fields
        below; providing none, or more than one, returns a validation error.
      properties:
        website_url:
          description: |
            Company website. Accepts `http`/`https`, with or without `www`.
          type: string
        domain:
          description: >
            Company domain or a domain alias - e.g. `tryspecter.com` resolves to
            Specter.
          type: string
          example: stripe.com
        linkedin_url:
          description: |
            Company LinkedIn URL. Accepts `http`/`https`, with or without `www`.
          type: string
        name:
          description: >
            Company name (at least 3 characters). Fuzzy-matched; may return
            several ranked candidates.
          type: string
          example: Stripe
      additionalProperties: false
      title: CompanyResolveIdentifier
    BasicCompany:
      type: object
      properties:
        id:
          description: The Specter company ID; use it with the other company endpoints.
          type: string
          example: 5e3bc2b700c8f4c966ad2bbd
        name:
          description: The company's main public name.
          type: string
          example: Stripe
        domain:
          description: The domain of the website, can have a sub-domain.
          type: string
          example: stripe.com
        hq:
          $ref: '#/components/schemas/HQ'
          description: The company's HQ location.
        tagline:
          description: A concise description of what the company does.
          type: string
          example: >-
            Stripe provides financial infrastructure for businesses to accept
            payments and grow revenue.
        founded_year:
          description: The year the company was founded.
          type: number
          nullable: true
          example: 2010
        match_confidence:
          description: >
            How closely the company matches the query, from 0 to 1. Relative to
            the other results in this response; not comparable across searches.
          type: number
          example: 1
      required:
        - id
        - name
        - hq
        - match_confidence
      additionalProperties: false
    ApiKeyMissing:
      properties:
        errorCode:
          description: API_KEY_MISSING
          example: API_KEY_MISSING
          type: string
        message:
          description: No API Key was presented on the header X-API-KEY
          example: No API Key was presented on the header X-API-KEY
          type: string
    ApiKeyNotValid:
      properties:
        errorCode:
          description: API_KEY_NOT_VALID
          example: API_KEY_NOT_VALID
          type: string
        message:
          description: API key present, but not valid
          example: API key present, but not valid
          type: string
    HQ:
      properties:
        city:
          description: City for the location.
          type: string
          example: South San Francisco
        state:
          description: >-
            State for the location, outside of America will relate to the
            country and region.
          type: string
          example: California
        country:
          description: Country for the location.
          type: string
          example: United States
        region:
          description: Use `continent` instead.
          type: string
          example: North America
          deprecated: true
        continent:
          description: The continent the HQ is in.
          type: string
          example: North America
        regions:
          description: Any regions that the HQ is in.
          type: array
          items:
            type: string
          example:
            - San Francisco Bay Area
      required:
        - city
        - state
        - country
        - region
      additionalProperties: false
      title: HQ
      type: object
  responses:
    CompanyResolveResponse:
      description: >
        One result group per input identifier, in the same order as
        `to_resolve`.
      content:
        application/json:
          schema:
            type: array
            items:
              type: object
              properties:
                query:
                  $ref: '#/components/schemas/CompanyResolveIdentifier'
                  description: The (normalized) identifier this group resolves.
                matches:
                  description: >
                    Matching companies. Empty when nothing matched; several
                    ranked candidates are possible for a `name` query.
                  type: array
                  items:
                    $ref: '#/components/schemas/BasicCompany'
              required:
                - query
                - matches
              additionalProperties: false
    Unauthorized:
      description: Unauthorized
      content:
        application/json:
          schema:
            oneOf:
              - $ref: '#/components/schemas/ApiKeyMissing'
              - $ref: '#/components/schemas/ApiKeyNotValid'
    Forbidden:
      description: Forbidden - There is no permissions to use the endpoint
      content:
        application/json:
          schema:
            type: object
            properties:
              errorCode:
                description: NOT_PERMITTED
                type: string
                example: NOT_PERMITTED
              message:
                type: string
                description: You do not have permission to access this resource.
                example: You do not have permission to access this resource.
            required:
              - errorCode
              - message
    RateLimits:
      description: Too Many Requests - API Rate limit exceeded
      content:
        application/json:
          schema:
            type: object
            required:
              - errorCode
              - message
            properties:
              errorCode:
                type: string
                description: RATE_LIMITED
              message:
                type: string
                description: You have been rate-limited
      headers:
        X-RateLimit-Limit:
          schema:
            type: integer
          description: The total rate limit allowed for this endpoint
        X-RateLimit-Remaining:
          schema:
            type: integer
          description: The number of requests remaining
        X-RateLimit-Reset:
          schema:
            type: number
            format: float
          description: The number of seconds until the rate limit resets
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-API-Key

````