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

# Find phone

> Find a phone number by lead ID, LinkedIn URL, or by name and company. Billed only when a phone number is found.

## Use Case:

Find a phone number by `lead_id`, `linkedin_url`, or by `first_name` + `last_name` + `company`.

## Pricing

This is a billable endpoint — you are charged only for each phone number found. If no phone is found, the request is free.

<Tip>Your price decreases automatically as your lifetime spend grows. [Check your current tier and pricing →](https://beta.generect.com/settings/billing)</Tip>


## OpenAPI

````yaml post /api/v1/phone/find/
openapi: 3.0.3
info:
  title: Generect API
  description: >-
    Welcome to the Generect API documentation. Here we will help you integrate
    and use our API.


    API base url: `https://api.generect.com` — every path below is relative to
    this host. Newer endpoints live under `/api/v1/...`, legacy endpoints under
    `/api/...`; use each path exactly as documented.

    Protocol: `HTTPS`


    # Authentication


    Get your API token from the Generect app settings and send it in the
    `Authorization` header with the required `Token` prefix.


    Example: `Authorization: Token xxxxxxxxx`


    # Rate limits


    You can request data depending on your data plan and account balance
    (default: 10000/month). Pricing depends on the operation and the number of
    results returned, and may increase with additional data flags. For exact
    pricing, see each endpoint's Pricing section or your billing settings:
    https://beta.generect.com/settings/billing


    # Note


    _Every endpoint must include the trailing `/`. Requests without the trailing
    slash may fail._
  version: 1.0.0
  contact: {}
servers:
  - url: https://api.generect.com
security:
  - apiKey: []
tags:
  - name: 1. Auth
    description: Login and get user info
  - name: 2. Transactions
    description: List of latest transactions in your account
  - name: 3. Leads
    description: Fetch information about leads by _link/name/ICP_.
  - name: 4. Companies
    description: Fetch information about companies by link/name/ICP.
  - name: 5. Preview
    description: Search masked database leads for preview and reveal workflows.
  - name: 6. Enrich
    description: Enrich leads and companies by internal or external identifiers.
  - name: 7. Email
    description: Find and validate email addresses.
  - name: 8. Accounts
    description: Account profile, usage, and transactions.
  - name: 9. Search
    description: Database and realtime lead, company, and company-lead search.
  - name: 10. Phone
    description: Find phone numbers for leads.
  - name: 11. Webhooks
    description: Register and manage async job notifications.
paths:
  /api/v1/phone/find/:
    post:
      tags:
        - 10. Phone
      summary: Find phone
      description: >-
        Find a phone number by lead ID, LinkedIn URL, or by name and company.
        Billed only when a phone number is found.
      requestBody:
        required: true
        content:
          application/json:
            schema:
              oneOf:
                - title: By Lead ID
                  type: object
                  required:
                    - lead_id
                  properties:
                    lead_id:
                      type: string
                      description: >-
                        Generect lead identifier from Search, Preview, or
                        Enrich.
                      example: ACwAAAE9bk0BxY7Qf2mN4pR8sT1vW3zA5cE6gH9
                - title: By LinkedIn URL
                  type: object
                  required:
                    - linkedin_url
                  properties:
                    linkedin_url:
                      type: string
                      description: LinkedIn profile URL.
                      example: https://www.linkedin.com/in/jordan-ellis
                - $ref: '#/components/schemas/PhoneFindByNameRequest'
      responses:
        '200':
          description: Phone finder result
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PhoneFindResponse'
              examples:
                Found:
                  value:
                    data:
                      lead_id: ACwAAAE9bk0BxY7Qf2mN4pR8sT1vW3zA5cE6gH9
                      phone:
                        number: '+14155550123'
                        status: FOUND
                        type: mobile
                        country: US
                    meta:
                      amount_charged: 0.4
                Not found:
                  value:
                    data:
                      lead_id: ACwAAAE9bk0BxY7Qf2mN4pR8sT1vW3zA5cE6gH9
                      phone:
                        number: null
                        status: NOT_FOUND
                    meta:
                      amount_charged: 0
        '400':
          description: Validation error or insufficient balance.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              examples:
                Validation error:
                  value:
                    status: error
                    status_code: 400
                    detail:
                      non_field_errors:
                        - >-
                          Provide one of: lead_id, linkedin_url, or
                          first_name+last_name+company.
                Insufficient funds:
                  value:
                    status: error
                    status_code: 400
                    detail: Insufficient funds in the account.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          $ref: '#/components/responses/Forbidden'
components:
  schemas:
    PhoneFindByNameRequest:
      title: By Name and Company
      type: object
      required:
        - first_name
        - last_name
        - company
      properties:
        first_name:
          type: string
          description: Lead's first name.
          example: John
        last_name:
          type: string
          description: Lead's last name.
          example: Doe
        company:
          type: string
          description: Company name or domain where the lead works.
          example: microsoft.com
        linkedin_url:
          type: string
          description: Optional LinkedIn profile URL to improve match accuracy.
          example: https://www.linkedin.com/in/jordan-ellis
    PhoneFindResponse:
      type: object
      properties:
        data:
          type: object
          properties:
            lead_id:
              type: string
              nullable: true
              description: Resolved lead identifier, when the input matched a lead.
            phone:
              type: object
              properties:
                number:
                  type: string
                  nullable: true
                  description: Phone number in E.164 format; null when not found.
                status:
                  type: string
                  enum:
                    - FOUND
                    - NOT_FOUND
                type:
                  type: string
                  description: >-
                    Number type (mobile, fixed_line, voip, ...). Present when
                    found.
                country:
                  type: string
                  description: ISO country code. Present when found.
        meta:
          $ref: '#/components/schemas/Meta'
    Error:
      type: object
      description: Standard error envelope returned for 4xx/5xx responses.
      properties:
        status:
          type: string
          example: error
        status_code:
          type: integer
          example: 400
        detail:
          description: >-
            Human-readable message (string) for most errors, or a field-level
            validation map ({ field: [messages] }) for 400 validation errors.
          example: Insufficient funds in the account.
    Meta:
      type: object
      description: Operation metadata returned in every data/meta response.
      required:
        - amount_charged
      properties:
        amount_charged:
          type: number
          description: >-
            Actual amount charged for this request in USD, computed from your
            pricing tier. 0 for free operations and for not-found results (No
            Data — No Charge).
        status:
          type: string
          description: Set to "error" when the operation finished with an error.
        error:
          type: string
          description: Error details; present only when the operation failed.
        time_cached:
          type: string
          format: date-time
          description: >-
            When the cached result set was originally collected (returned by
            database company search when results are served from a previous
            identical search).
  responses:
    Unauthorized:
      description: Missing or invalid API token.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            status: error
            status_code: 401
            detail: Authentication credentials were not provided.
    Forbidden:
      description: Authenticated, but the account/plan is not allowed to use this endpoint.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            status: error
            status_code: 403
            detail: You do not have permission to perform this action.
  securitySchemes:
    apiKey:
      type: apiKey
      in: header
      name: Authorization
      description: 'Use the required Token prefix. Example: Authorization: Token xxxxxxxxx'

````