Skip to content

Adjust Install Attrib REST API

Jim Lake edited this page Dec 6, 2014 · 4 revisions

Welcome to the Data Cortex Adjust Ingest API.

API Endpoint

All calls are made on the api endpoint:

https://api.data-cortex.com

Request

Calls to the API are made with a POST to the API endpoint.

Note: One of idfa, idfv, gps_adid, mac_md5 must be present.

POST /<org>/1/adjust_track

<org> - string - Should be replaced with the organization short name.

Request Parameters

The request should contain a JSON body. The client should be sure to set the the Content-Type header to "application/json". Arguments are required unless noted otherwise.

api_key - string - The api key specific to this application. Applications can have more than 1 API key, but can not be shared between applications.

idfa - string - (optional) iOS IDFA

idfv - string - (optional) iOS IDFV

gps_adid - string - (optional) Google Play Services Advertising ID.

mac_md5 - string - (optional) MD5 of device MAC.

network_name - string - (optional) Network name for install attribution. 32 character maximum.

campaign_name - string - (optional) Campaign name for install attribution. 32 character maximum.

site_name - string - (optional) Site name for install attribution. 32 character maximum.

adgroup_name - string - (optional) Adgroup name for install attribution. 32 character maximum.

creative_name - string - (optional) Creative for install attribution. 32 character maximum.

Response

The API responds with the following depending on the result.

Success

Event has been received.

HTTP/1.1 200 OK
Cache-Control: no-cache, no-store, must-revalidate
Content-Type: text/plain; charset=utf-8
Content-Length: 2
Date: Thu, 04 Dec 2014 22:04:42 GMT
Connection: keep-alive

OK

Bad Request

Bad request. Check with Data Cortex documentation and verify that you are sending all required fields and valid data types in those fields.

 HTTP/1.1 400 Bad Request

Auth Failure

Bad API key. Check with Data Cortex and verify your API key. Productions clients should treat this as a fatal error.

 HTTP/1.1 403 Forbidden

All other error codes.

Internal server error. Clients should treat these as soft errors and retry.

 HTTP/1.1 500 Internal Server Error

Clone this wiki locally