Manage destinations (aka Customer Phone Numbers)
Destinations are alternate way of managing RingPools. Learn more about RingPools here.Property | Type | Value |
|---|---|---|
id | integer (read-only) | The internal Invoca id of the Destination. |
country_code | string | Country code of the phone number. |
phone_number | string | Phone number of the Destination. |
primary_url | string | Website or page URL on which the destination is applied. |
requested_destination_name | string (read-only) | Alias for the destination. Auto-generated names. |
advertiser_campaign | ||
id_from_network | string | The network object_id for this Advertiser Campaign. Unique within network. Not required when auto-generation is enabled at network level. |
name | string | Campaign name. |
status | string | Current campaign state. |
dynamic_number_pool | ||
id | integer (read-only) | The internal Invoca id of the RingPool. |
id_from_network | string (required) | Network specific id of the RingPool. Unique within network. Not required when auto-generation is enabled at network level. |
name | string | Arbitrary string. Names the RingPool. |
object_url | string (read-only) | URL for reaching the RingPool in the UI. |
lifetime_seconds | integer | The guaranteed minimum time that the number will be allocated for this RingPool. |
max_pool_size | integer | The maximum amount of phone numbers to be allotted at one time. |
preferred | boolean | true or false. Selects this RingPool if the advertiser has multiple RingPools for the campaign and the web integration code does not specify which pool to use. |
destination_phone_number | A phone number to be associated with the RingPool. | When using Destinations UI or the forward to destination IVR node, this number will be used. |
fill_immediately | boolean | When true, the ringpool will immediately be filled with phone numbers up to the max_pool_size, if numbers are available. When false, the pool will initially fill at 10% capacity to conserve phone number usage. The ringpool will increase phone numbers based on ringpool autoscaling settings and traffic volume. |
https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers.json
Get all Destinations
Get all Destinations
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 |
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:
|
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 |
https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers.jsonResponse Code: 200Response Body:Get a Destination
Get a Destination
Examples
Read a DestinationEndpoint:https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers/<customer_phone_number_id>.jsonResponse Code: 200Response Body:Delete a Destination
Delete a Destination
Examples
Delete a DestinationEndpoint:https://invoca.net/api/2022-08-01/<network_id>/customer_phone_numbers/<customer_phone_number_id>.jsonResponse Code: 200Response Body: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.