Skip to main content

Manage destinations (aka Customer Phone Numbers)

Destinations are an alternate way of managing RingPools. Learn more about RingPools here. Endpoint: https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers.json
Possible options that can be provided in the API request.

Property

Type

Value

limit

integer (optional) (Default 100)

Number of objects to be returned in a single request. If not provided, first 100 objects will be returned.

start

integer (optional) (Default 0)

First x number of objects to skip in the response. If not provided, the response will start from the first available object.

query

string (optional)

Search string to search by phone number.

If not provided, all objects will be returned given no other filters are included.

status

string (optional)

To filter results by a specific type.

If not provided, all objects will be returned given no other filters are included.

Possible values include:

  • ignored: Fetches only destinations that were ignored.

  • tracked: Fetches only destinations that have a ringpool associated with them.

  • discovered: Fetches only destinations that were neither ignored nor have a ringpool associated with them.

sort_by

string (optional) (Default id)

Sort the result by a specific column.

sort_dir

string (optional) (Default asc)

Sorting direction for the objects being returned. Possible values include asc and desc.

ExamplesRead all Destinations as an array.Endpoint:https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers.jsonResponse Code: 200Response Body:

Examples

Read a DestinationEndpoint:https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers/<customer_phone_number_id>.jsonResponse Code: 200Response Body:

Examples

Delete a DestinationEndpoint:https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers/<customer_phone_number_id>.jsonResponse Code: 200Response Body:
NOTE: Creating & Deleting Destinations
Creating a Destination via this endpoint isn’t possible. A Destination can be made alongside a RingPool that it’ll be associated with via the RingPool endpoint (Documentation).
The Destination can be deleted via this endpoint, but if the associated RingPool is going to be deleted as well, you can save a request by utilizing the delete_detected_phone_number parameter in the RingPool endpoint.
Last modified on September 28, 2026