Skip to main content
Notice: Please contact your CSM or the support team to request access.
The Calls In Progress API is used for interacting with pre-call insights for live calls as part of PreSense. It can retrieve information during a call. Calls become available via the API as soon as they are transferred to the campaign’s destination. Once the call is complete, it is no longer available via the API. For authentication, use an API token. See Manage API Credentials for details.

Find Calls in Progress

Perform a GET request to query calls currently in progress for the specified organization. Sending only the required parameters will return all current calls. The custom_data field contains the Marketing Data Fields (aka Custom Data Fields) that have values when the call is received. Each custom data field will include the current value and the source of that value. These values can come from your Invoca Tag, values applied to Networks/Advertisers/Campaigns/Promo Numbers, or from data returned by a Real-Time Routing Webhook. If you have Enhanced Caller Profiles (ECP) enabled, the demographics_data field will contain any ECP data that is available for the caller.

Query Parameters

General Fields

Below is a general list of data points that are available via the API; some fields may not be available depending on their organization type and/or configuration.

Examples

GET /calls_in_progress/current_calls — Get all available calls in progress for the specified organization

Be sure to use your own organization_type and id. Endpoint:
Response Code: 200 Response Body:

GET /calls_in_progress/current_calls — Get calls in progress by transaction id

Get calls in progress for transaction id ABCD1234-ABCD1234. Be sure to use your own organization_type and id. current_calls will be ordered by bridge_start_time, most recent first. Endpoint:
Parameters: transaction_id is required for this request Response Code: 200 Response Body:

GET /calls_in_progress/current_calls — Get calls in progress by call record id

Get calls in progress for call record id Z6E5-C7397356976E. Be sure to use your own organization_type and id. This can return multiple results if there are multiple transactions for the call in progress. current_calls will be ordered by bridge_start_time, most recent first. Endpoint:
Parameters: call_record_id is required for this request Response Code: 200 Response Body:

GET /calls_in_progress/current_calls — Get calls in progress by external unique id

Get calls in progress for the External Unique ID mycalls00001. Be sure to use your own organization_type and id. Endpoint:
Parameters: external_unique_id is required for this request Response Code: 200 Response Body:

GET /calls_in_progress/current_calls — Get calls in progress by calling and destination phone numbers

Get calls in progress for the calling phone number 530-999-9999 and destination phone number 855-559-5599. Be sure to use your own organization_type and id. This example is for an organization with Enhanced Caller Profiles enabled, so the demographics data is included in the response. Endpoint:
Parameters: calling_phone_number and destination_phone_number are required for this request Response Code: 200 Response Body:

Using the API for Attribution

For customers looking to enhance attribution accuracy, the API offers a streamlined payload with Invoca call identifiers, including the Transaction Id and Call Record Id for Exact Match Attribution. By utilizing these identifiers, customers can avoid the need for fuzzy matching of calls when attributing data via Invoca APIs. This is particularly advantageous for those who often deal with repeat callers.
Notice: When leveraging the API for this attribution-focused use case, customers will not receive any pre-call data and will not be obligated to purchase PreSense.Both use cases utilize the same endpoint, and the API accepts the same query parameters, irrespective of whether pre-call data is present.

Examples

GET /calls_in_progress/current_calls — Retrieve a specific call by Transaction ID

Get calls in progress for transaction id ABCD1234-ABCD1234. Be sure to use your own organization_type and id. current_calls will be ordered by bridge_start_time, most recent first. Endpoint:
Parameters: transaction_id is required for this request Response Code: 200 Response Body:

GET /calls_in_progress/current_calls — Retrieve a specific call by Call Record ID

Get calls in progress for call record id Z6E5-C7397356976E. Be sure to use your own organization_type and id. This can return multiple results if there are multiple transactions for the call in progress. current_calls will be ordered by bridge_start_time, most recent first. Endpoint:
Parameters: call_record_id is required for this request Response Code: 200 Response Body:

Response Codes

Remember to check the HTTP status code returned. This helps greatly when debugging.
Last modified on August 18, 2026