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

# List phone numbers connected to this workspace

> Local rows synced from Meta, not a live Graph API call. Use `phone_number_id` / `whatsapp_business_account_id` from here as the `phone_number` / `whatsapp_business_account_id` values on POST /messages/.



## OpenAPI

````yaml /openapi.json get /api/v1/phone-numbers/
openapi: 3.0.3
info:
  title: ChatBridge Public API
  version: 1.0.0
  description: >-
    Customer-facing REST API for ChatBridge — contacts, conversations, messages,
    templates, team, catalogue, tickets, and WhatsApp Flows. Authenticate with a
    workspace API key: `Authorization: Bearer cb_...`. See
    https://github.com/algosmiths/whatschat/blob/main/public_api.md for the full
    scope/versioning reference.
servers:
  - url: https://api.algosmiths.com
    description: Production
security: []
paths:
  /api/v1/phone-numbers/:
    get:
      tags:
        - Account Health
      summary: List phone numbers connected to this workspace
      description: >-
        Local rows synced from Meta, not a live Graph API call. Use
        `phone_number_id` / `whatsapp_business_account_id` from here as the
        `phone_number` / `whatsapp_business_account_id` values on POST
        /messages/.
      operationId: phone_numbers_list
      responses:
        '200':
          content:
            application/json:
              schema:
                type: array
                items:
                  $ref: '#/components/schemas/PublicPhoneNumber'
          description: ''
      security:
        - ApiKeyAuth: []
        - tokenAuth: []
        - CookieAuth: []
components:
  schemas:
    PublicPhoneNumber:
      type: object
      description: >-
        Public-API-safe subset of PhoneNumberSerializer — an allow-list, not an

        exclude-list, so a new sensitive field added to PhoneNumber later
        doesn't

        silently leak to third-party API keys the way it would with `exclude`.

        Deliberately never includes `pin` (Fernet-encrypted, but still not

        third-party-key material).
      properties:
        phone_number_id:
          type: string
          maxLength: 255
        display_phone_number:
          type: string
          maxLength: 25
        verified_name:
          type: string
          maxLength: 255
        quality_rating:
          type: string
          maxLength: 60
        messaging_limit_tier:
          type: string
          maxLength: 64
        whatsapp_business_account_id:
          type: string
          readOnly: true
      required:
        - display_phone_number
        - phone_number_id
        - quality_rating
        - verified_name
        - whatsapp_business_account_id
  securitySchemes:
    ApiKeyAuth:
      type: http
      scheme: bearer
      bearerFormat: cb_...
      description: >-
        Workspace API key, e.g. `Authorization: Bearer cb_live_...`. Create one
        in Settings → API Keys. See public_api.md § 3 for scopes.
    tokenAuth:
      type: apiKey
      in: header
      name: Authorization
      description: Token-based authentication with required prefix "Token"
    CookieAuth:
      type: apiKey
      in: cookie
      name: token
      description: Dashboard session cookie — internal use only, not the public contract.

````