Find Calls in Progress
Perform aGET 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 all available calls in progress for the specified organization
Get all available calls in progress for the specified organization
Example
Get all available calls in progress for the specified organization. Be sure to use your own organization_type and id.Endpoint:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>Response Code: 200Response Body:Get calls in progress by transaction id
Get calls in progress by transaction id
Example
Get calls in progress for transaction idABCD1234-ABCD1234. Be sure to use your own organization_type and id.current_calls will be ordered by bridge_start_time, most recent first.Endpoint:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>&transaction_id=ABCD1234-ABCD1234Parameters: transaction_id is required for this requestResponse Code: 200Response Body:Get calls in progress by call record id
Get calls in progress by call record id
Example
Get calls in progress for call record idZ6E5-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:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>&call_record_id=Z6E5-C7397356976EParameters: call_record_id is required for this requestResponse Code: 200Response Body:Get calls in progress by external unique id
Get calls in progress by external unique id
Example
Get calls in progress for the External Unique IDmycalls00001. Be sure to use your own organization_type and id.Endpoint:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>&external_unique_id=mycalls00001Parameters: external_unique_id is required for this requestResponse Code: 200Response Body:Get calls in progress by calling and destination phone numbers
Get calls in progress by calling and destination phone numbers
Example
Get calls in progress for the calling phone number530-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:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>&calling_phone_number=5309999999&destination_phone_number=8555595599Parameters: calling_phone_number and destination_phone_number are required for this requestResponse Code: 200Response 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
Retrieve a specific call by Transaction ID
Retrieve a specific call by Transaction ID
Example
Get calls in progress for transaction idABCD1234-ABCD1234. Be sure to use your own organization_type and id.current_calls will be ordered by bridge_start_time, most recent first.Endpoint:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>&transaction_id=ABCD1234-ABCD1234Parameters: transaction_id is required for this requestResponse Code: 200Response Body:Retrieve a specific call by Call Record ID
Retrieve a specific call by Call Record ID
Example
Get calls in progress for call record idZ6E5-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:https://invoca.net/api/2022-08-01/calls_in_progress/current_calls.json?id=<organization_id>&organization_type=<organization_type>&call_record_id=Z6E5-C7397356976EParameters: call_record_id is required for this requestResponse Code: 200Response Body: