All interfaces use REST. This makes them easy to predict as they use HTTP and its existing verbs to Create, Read, Update, and Delete objects. Any language that supports HTTP can access these interfaces. Create and Update are idempotent operations.
|Create||POST||Object is created. If it already exists, it is updated.|
|Read||GET||Object is read.|
|Update||PUT||Object is created. If it already exists, it is updated.|
|Delete||DELETE||Object is deleted. If the object has already been deleted, does nothing.|
HTTP Status codes are used to indicate success or failure. The set of status codes returned by the Network Integration API are:
|401||Failure. Access is not authorized.|
|403||Failure. Request arguments are invalid.|
|404||Failure. The resource was not found.|
|500||Failure. Internal Service Error.|
* See the section on Error Handling for greater detail on response bodies for failure codes.
HTTPS is required for all API requests.
Authentication is performed using one of several approaches.
The preferred approach is to use Invoca API tokens. See Manage API Credentials for more information.
Some API endpoints will accept HTTP(S) Basic Authentication, which authenticates using a username and password in the request header.
Additionally, session login authentication is sufficient as an alternative. This is so that you can test an API URL simply by logging in to the platform first as a Network Role of ‘Super’ (full access user) and then pasting the URL into the browser.
Most interfaces are designed to be idempotent, meaning that it is harmless to call them more than once with the same parameters. Subsequent calls to an interface have no side effects, and return the same result.
Most updates expect a complete copy of the object, making Update and Create interchangeable. This means that errors tend to be corrected over time. Campaign Terms are an exception to this due to their complexity (see Advertiser Campaigns for more).
The API version is given as a date in the path.
All APIs are accessed through the dedicated subdomain of invoca.net that is used for the network. For example, a network named “LeadTrust” might be assigned leadtrust.invoca.net. We recommend that, when making your API calls, you place your <network_id> after the API version in the url.
Request Parameter Format & Response Body Format¶
Previous versions of the API accepted form‐encoded style parameters in the request and used XML as the output format. As of 2019-05-01, all new feature development has switched to JSON format for both request and response. Previous XML functionality will continue to be supported via the 2013‐03‐22 version of the API (please contact firstname.lastname@example.org for more information on previous versions).