Skip to main content
Similar to Promo Numbers, because these are generated by Invoca, the interface is idempotent. By default, RingPools will capture params based on your Marketing Data Dictionary. Learn more about RingPools here. Endpoint: https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools/<ring_pool_id_from_network>.json
NOTE: Creating DestinationsIf a valid phone number is given for destination_phone_number as part of the POST request, a Destination, aka Customer Phone Number, will be generated and associated with the created RingPool.Additionally, if the network is configured to use Tag Destinations, the obfuscated_tag_id for a JsTag must be given as well.

GET /ring_pools

Read all RingPools as an array. Endpoint: https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools.json Response Code: 200 Response Body:

GET /ring_pools/<ring_pool_id>

Read a RingPool. Endpoint: https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools/<ring_pool_id_from_network>.json Response Code: 200 Response Body:

POST /ring_pools

Create a RingPool. Endpoint: https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools.json Format: application/json Request Body:
Response Code: 201 Response Body: Same as a GET response, includes all the RingPool properties.

PUT /ring_pools/<ring_pool_id>

Update a RingPool. Endpoint: https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools/<ring_pool_id_from_network>.json Format: application/json Request Body:
Response Code: 200 Response Body: Same as a GET response, includes all the RingPool properties.

DELETE /ring_pools/<ring_pool_id>

Delete a RingPool. Endpoint: https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools/<ring_pool_id_from_network>.json Format: application/json Response Code: 200 Response Body:

Local RingPool API

Local RingPool Creation

The API provides the ability to create RingPools with additional information that specifies them as being ‘Local’ RingPools. These Local RingPools use local numbers that are determined by the parameters passed in by the user of the API. If a local phone number cannot be found the pool fills those slots (max_pool_size) with toll free numbers instead. When you POST with the correct parameters the Local RingPool is created and the allocation of local numbers happens later (approx. 10 minutes). This capability is JSON-only.

POST

https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools.json Content Type: application/json Response Code: 200 Request Body
Response Body Same as a GET response, includes all the RingPool properties.

Error Handling

Forbidden – 403

POST https://invoca.net/api/@@HOURS_OF_OPERATION_API_VERSION/<network_id>/advertisers/<advertiser_id_from_network>/advertiser_campaigns/<advertiser_campaign_id_from_network>/ring_pools.json Content Type: application/json Response Code: 403 Request Body
Response Body
Last modified on August 18, 2026