Usage

Base URL

Prior to using the Quantive Results REST API you must determine your REST API base URL.

The base URL for using the Quantive Results REST API varies based on where your account is located. Before using the API you must determine in which data center your Quantive Results account lives. It can be either EU or US.

• EU:

  • If your account URL is https://yourAccountDomain.quantive.com then you are on the EU data center.
  • Your API base URL is: https://app.quantive.com/results/api/v1/

• US:

  • If your account URL is https://yourAccountDomain.us.quantive.com then you are on the US data center.
  • Your API base URL is: https://app.us.quantive.com/results/api/v1

Once you’ve determined your API base URL, you can work with each public endpoint documented here by appending its name to the base URL.

This API reference use the following convention for the endpoint URLs https://app.(us./as./sa.)quantive.com. You must determine the correct API base URL based on your data center. It can either be https://app.quantive.com/results/api/v1/ or https://app.us.quantive.com/results/api/v1/.

Example:

The Tasks API endpoint URL is /tasks. To work with the Tasks API you must use the following URL:

• EU: https://app.quantive.com/results/api/v1/tasks
• US: https://app.us.quantive.com/results/api/v1/tasks

V2 Endpoints

The endpoints documented in the v2 section of this API reference have their Base URL as:

• EU: https://app.quantive.com/results/api/v2/
• US: https://app.us.quantive.com/results/api/v2/

Account ID

Any request to the Quantive Results REST API requires you to specify your account Id. You must pass it as a HTTP header with the following properties:

• Name: gtmhub-accountid
• Value: your account Id

curl: "api_endpoint_here" \
  -H "gtmhub-accountid: 5dd52936b1d01a0001ecb1b5" 

For more information on finding your account Id, check this article: <a href="https://help.quantive.com/en/articles/1273148-quantive-results-api-quickstart">API Quickstart</a>

Authentication

All Quantive Results REST API endpoints are protected and require you to pass an API token so you can authenticate your request. For more information on generating your API token, check API Quickstart. You must pass the API token as an HTTP header with the following properties:

• Name: Authorization

• Value: Bearer your API token value, for example "Bearer apiToken"

curl: "api_endpoint_here" \
  -H 'Authorization: Bearer apiToken'

You must replace apiToken with your personal API key.