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.Authentication
The API uses OAuth to validate access. The OAuth Token can be passed in two ways. The first way is to pass the OAuth Token in the header of the request. The second is to pass the OAuth Token like any other query parameter. Please note that the OAuth Token is a required parameter. 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:
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:
https://invoca.net/api/2020-10-01/affiliates/transactions/<affiliate_id>.<format>