Skip to main content

Publisher / Affiliate

Signal Transactions Rollup

If you’re upgrading from API versions older than 2020-10-01 we suggest testing to familiarize yourself with the updated Signal data structure.For more information, view the support documentation for best practices in accessing Invoca Call Data via the Transactions API.

URL

The API follows REST conventions. Perform an HTTPS GET to the URL with the format in which you’d like to receive data. The following response formats are supported, where 33 is the affiliate id. Endpoint: https://invoca.net/api/@@TRANSACTION_API_VERSION/affiliates/transactions/<affiliate_id>.<format>

Authentication

The API uses OAuth to validate access. Pass the OAuth Token in the Authorization header of the request. The OAuth Token is required. OAuth Tokens may be generated from the Manage API Credentials page.

Query Parameters

The API takes the following optional query parameters: In order to ensure that all transactions are returned when using the from= and to= date query parameters, you should store the last transaction id you have downloaded and pass it as the start_after_transaction_id to the next request so long as you do not change the date range. Once you update the date range, the best practice is to omit the start_after_transaction_id param for the first request, then use the last transaction id you have downloaded until the date range is complete. This is because using from and to params sorts transactions in relation to the call start time, not the transaction time. Typical usage on the polling interval is to repeatedly call the API until no rows are returned, meaning you have downloaded all transactions. Please note, the “to” and “from” date range parameters are both necessary, providing only one or the other will not filter the results. We provide a helpful constant that can be used in the include_columns and exclude_columns options:
  • $invoca_default_columns — represents the default set of columns provided by the Transactions API for your requested version.

Response

General Parameters

RingPool Parameters

Additional Feature Parameters

Examples

These examples use CURL, and are using the following fake OAuth API token: YbcFH Note: the -k option asks curl to not bother checking the SSL certificate authority chain as that requires extra configuration. Example 1: Get the next 20 transactions that occurred after transaction id C624DA2C-CF3367C3:
Example 2: Get 50 rows from a specific time period with only the transaction_id and duration columns:
Example 3: Get 50 rows that exclude a few columns such as city and region:
Example 4: Get All Transactions from a specific time period that are of transaction_type Signal:
Example 5: Get All Transactions from a specific time period that are of transaction_type Post Call Event:
Example 6: Get All Transactions from a specific time period that are of transaction_type Call and Signal:
Last modified on August 18, 2026