CloudTalk Numbers API

All data you can get about your numbers.

Business capability
Voice & Telephony AE-150.50

Operations 3

GET /numbers/index.json List numbers #
POST /numbers/edit/{id}.json Edit a number #
DELETE /numbers/clear/{id}.json Unregister a number #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/cloudtalk:cloudtalk-numbers-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

cloudtalk-numbers-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: CloudTalk Numbers API
  description: '# Introduction

    Welcome to CloudTalk API reference! Many of these businesses use the CloudTalk API to automate and enhance their customer support with CloudTalk Support. With CloudTalk we are re-building telco industry from the ground and taking it to the next level with first-class customer support system. Please find below the full documenation to CloudTalk. # API Overview


    The API is organized around the following resources:


    API Area | Description

    ----------------|-------------

    Calls | Browse your call history, download recordings and access all your calls data. Contacts | Create and update Contacts. Use filters to get lists of Contacts, or access their profiles individually. Numbers | Automate Numbers modifications. List all your numbers. Agents | Create or update your Agents, access their settings. Conversation Intelligence | Get Conversation Intelligence data about your calls. VoiceAgent | Initiate VoiceAgent calls


    JSON is returned in all responses. XML is not supported. The API also uses common approaches for the following:


    Function | Description

    ----------------|-------------

    Data | API data is JSON encoded with UTF-8. API JSON is either a single object or a list of objects. Errors | 4xx and 5xx responses returning JSON with error codes

    Rate Limiting | Controls how many requests can be made in a time window

    HTTP | Methods are used in accordance with HTTP (GET POST and DELETE are the primary methods used) and resources are identified using URIs. All API requests are sent over HTTPS. ## Authentication


    This is an HTTPS-only API. Authentication is based on API Access Key ID and Access Key Secret. The API Access Key ID and Access Key Secret is passed via HTTP Basic Authentication. Basic Auth credentials are used to determine on which project should this request be executed on. List of all Basic Auth credentials for the project can be found by Administrators in the CloudTalk Dashboard under Account → Settings → API Keys (https://dashboard.cloudtalk.io/menu/account/settings/API-keys). To try the API via curl on the command-line, the general form used would be:

    ```

    curl -u ACCESS_KEY_ID:ACCESS_KEY_SECRET API_URL

    ```


    For instance, you would execute:

    ```

    curl -u ABCDEFGHIJTESTKEY1:X05Dg4c331c3h61An https://my.cloudtalk.io/api/calls/index.json

    ```


    ## Usage


    The API may rate limit submission of requests for your application. Such limits are managed as an allowed number of operations per time window, where an operation might be read or an update. In that case a **''429 Too Many Requests''** response code will be returned along with the following headers -


    Header name | Description

    ----------------|-------------

    X-CloudTalkAPI-Limit | Maximum number of API requests allowed in the current time window. X-CloudTalkAPI-Remaining | Number of API requests left in the current window. X-CloudTalkAPI-ResetTime | Time when rate limit window will be reset as a Unix timestamp. Note that the default rate limit is **60 operations per minute per company**. If you need to make more requests, please contact our support with detailed explanation of your use case. ## Response Envelopes


    **Note:** Conversation Intelligence doesn''t follow envelopes. The API returns one of three envelopes depending upon the request issued:


    1. Single Item Envelope

    2. Collections Envelope

    3. Error Envelope


    ### Single Item Envelope


    All dates/times are returned in ISO8601 format and in UTC timezone. ```

    Status: 200 OK

    {

    "responseData": {

    "id": 123,

    ... "created": "2018-01-10 12:34:56"

    }

    }

    ```


    ### Collections Envelope


    All dates/times are returned in ISO8601 format and in UTC timezone. ```

    Status: 200 OK

    {

    "responseData": {

    "itemsCount": 65,

    "pageCount": 3,

    "pageNumber": 1,

    "limit": 30,

    "data": [

    {

    "id": 123,

    ... "created": "2018-01-10 12:34:56"

    },

    {

    "id": 456,

    ... "created": "2017-10-19 09:21:29"

    },

    ...'
  contact:
    name: CloudTalk API Support
    url: https://www.cloudtalk.io/contact
  version: '1.7'
  x-logo:
    url: https://my.cloudtalk.io/img/logo-cloudtalk-color.png
servers:
- url: https://my.cloudtalk.io/api
security:
- basicAuth: []
tags:
- name: Numbers
  description: All data you can get about your numbers.
paths:
  /numbers/index.json:
    get:
      tags:
      - Numbers
      summary: List numbers
      description: Returns the phone numbers assigned to the account. Filter by `id`, `country_code`, `area_code`, what the number is `connected_to`, or `is_free` to show only numbers with no routing configured; page with `limit` and `page`.
      parameters:
      - name: id
        in: query
        description: Filter by number ID
        schema:
          type: integer
      - name: country_code
        in: query
        description: Filter by country calling code
        schema:
          type: integer
      - name: area_code
        in: query
        description: Filter by local area code. Area code cannot contain 0 at the beginning
        schema:
          type: integer
      - name: connected_to
        in: query
        description: Filter by route type. `0 = 'group'`, `1 = 'agent'`, `2 = 'conference room'`, `3 = 'fax'`
        schema:
          type: integer
          enum:
          - 0
          - 1
          - 2
          - 3
      - name: is_free
        in: query
        description: Filter by availability. `0 = 'taken'`, `1 = 'free'`
        schema:
          type: integer
          enum:
          - 0
          - 1
      - name: limit
        in: query
        description: Max. number of items in response data.
        schema:
          maximum: 1000
          minimum: 1
          type: integer
      - name: page
        in: query
        description: Number of page to return.
        schema:
          minimum: 1
          type: integer
      responses:
        '200':
          description: Numbers data
          content:
            application/json:
              schema:
                type: object
                properties:
                  responseData:
                    type: object
                    properties:
                      itemsCount:
                        type: integer
                        description: number of resources in the response
                        format: int64
                      pageCount:
                        type: integer
                        description: number of pages found
                        format: int64
                      pageNumber:
                        type: integer
                        description: current page in the response
                        format: int64
                      limit:
                        type: integer
                        description: number of objects sent per page
                        format: int64
                      data:
                        type: array
                        items:
                          type: object
                          properties:
                            CallNumber:
                              $ref: '#/components/schemas/CallNumber'
                required:
                - responseData
              example:
                responseData:
                  itemsCount: 3
                  pageCount: 1
                  pageNumber: 1
                  limit: 3
                  data:
                  - CallNumber:
                      id: '123'
                      country_code: '44'
                      area_code: '20'
                      internal_name: Sales support
                      caller_id_e164: 442012345678
                      is_redirected: false
                      connected_to: '1'
                      source_id: '4'
      operationId: getNumbersIndexJson
      x-operation-id-source: derived
  /numbers/edit/{id}.json:
    post:
      tags:
      - Numbers
      summary: Edit a number
      description: 'Updates the number identified by `id`. All three fields are optional: `internal_name` sets the number''s internal label, and `connected_to` with `source_id` set what it routes to. To strip a number''s routing entirely, use Unregister a number instead. Returns `404` if no number has that ID.


        Note the core API updates with `POST`, not `PUT`.'
      parameters:
      - name: id
        in: path
        description: Number ID to edit
        required: true
        schema:
          type: integer
      requestBody:
        content:
          application/json:
            schema:
              type: object
              properties:
                internal_name:
                  type: string
                  description: Internal name
                connected_to:
                  type: integer
                  description: Routing type. Where is the number connected. `0 = 'group'`, `1 = 'agent'`, `2 = 'conference room'`, `3 = 'fax'`
                source_id:
                  type: integer
                  description: Source ID of where is the number located, e.g. Agent ID, Group ID...
        required: true
      responses:
        '200':
          description: No error
          content:
            application/json:
              schema:
                type: object
                properties:
                  responseData:
                    type: object
                    properties:
                      status:
                        type: integer
                        description: Status code
                required:
                - responseData
              example:
                responseData:
                  status: 200
        '404':
          description: Not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorData'
              example:
                responseData:
                  status: 404
                  message: Not found.
        '406':
          description: Invalid input
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorInvalidData'
              example:
                responseData:
                  status: 406
                  message: Invalid input data.
                  data:
                    type:
                    - Please supply a valid type.
        '500':
          description: Something went wrong
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorData'
              example:
                responseData:
                  status: 500
                  message: Something went wrong.
      x-codegen-request-body-name: body
      operationId: postNumbersEdit{id}Json
      x-operation-id-source: derived
  /numbers/clear/{id}.json:
    delete:
      tags:
      - Numbers
      summary: Unregister a number
      description: Clear current route settings of the number. Number will be marked as free.
      parameters:
      - name: id
        in: path
        description: Number ID to unregister
        required: true
        schema:
          type: integer
      responses:
        '200':
          description: No error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/SuccessGeneralData'
              example:
                responseData:
                  status: 200
        '404':
          description: Number not found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorData'
              example:
                responseData:
                  status: 404
                  message: Not found.
        '500':
          description: Something went wrong
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorData'
              example:
                responseData:
                  status: 500
                  message: Something went wrong.
      operationId: deleteNumbersClear{id}Json
      x-operation-id-source: derived
components:
  schemas:
    ErrorInvalidData:
      type: object
      description: Validation-error envelope returned by the core API on `my.cloudtalk.io/api`. The payload is always wrapped in `responseData`.
      properties:
        responseData:
          type: object
          properties:
            status:
              type: integer
              description: HTTP status code
            message:
              type: string
              description: The error message
            data:
              type: object
              properties: {}
              description: Field-level detail explaining the error
          required:
          - status
          - message
      required:
      - responseData
    SuccessGeneralData:
      type: object
      description: Success envelope returned by the core API on `my.cloudtalk.io/api`. The payload is always wrapped in `responseData`.
      properties:
        responseData:
          type: object
          properties:
            status:
              type: integer
              description: Status code
      required:
      - responseData
    ErrorData:
      type: object
      description: Error envelope returned by the core API on `my.cloudtalk.io/api`. The payload is always wrapped in `responseData`.
      properties:
        responseData:
          type: object
          properties:
            status:
              type: integer
              description: HTTP status code
            message:
              type: string
              description: The error message
          required:
          - status
          - message
      required:
      - responseData
    CallNumber:
      type: object
      properties:
        id:
          type: integer
          description: Number ID
        country_code:
          type: integer
          description: Country calling code
        area_code:
          type: integer
          description: Local area code
        internal_name:
          type: string
          description: Internal name
        caller_id_e164:
          type: string
          description: Full number in international E.164 format
        is_redirected:
          type: boolean
          description: Is number redirected?
        connected_to:
          type: integer
          description: Routing type. Where is the number connected. `0 = 'group'`, `1 = 'agent'`, `2 = 'conference room'`, `3 = 'fax'`
        source_id:
          type: integer
          description: Source ID of where is the number located, e.g. Agent ID, Group ID...
      description: Number data
  securitySchemes:
    basicAuth:
      type: http
      scheme: basic
      description: HTTP Basic Authentication. Use your API Access Key ID as the username and your API Access Key Secret as the password. Generate keys in the CloudTalk Dashboard under Account -> Settings -> API Keys (https://dashboard.cloudtalk.io/menu/account/settings/API-keys).
x-provenance:
  method: harvested
  publisher: CloudTalk
  source: https://help.cloudtalk.io/api-reference/openapi.json
  note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
    stamped by stamp-openapi-provenance.py (roadmap#793)