Use the Adjust server-to-server API to connect your app to Adjust without changing your app code.
Authentication
The S2S API uses Bearer tokens for authentication. You MUST include your Adjust API token in an Authorization
header with each request you make to the Blocklist API.
If your organization has enabled Single Sign-On (SSO), contact your Adjust representative or email support@adjust.com for help with finding your API token.
For non-SSO accounts, API tokens are located in a user’s profile. To find your token, follow these steps:
- Select the account (user) icon.
- Select Account settings.
- Select the My profile tab.
- Your API Token is shown with your User Details. Select the copy button to copy the token to your system clipboard.
Reset your Adjust API token
You can reset your Adjust API token at any time. Resetting your token invalidates the old token. If you reset your Adjust API token, you MUST replace your old token anywhere that you’re using it. Requests made with an invalidated token are rejected by Adjust.
To reset your Adjust API token:
- Select the account (user) icon.
- Select Account settings.
- Select the My Profile tab.
- Your API Token is shown with your User details.
- Select Reset API token.
- Enter your account password in the modal that appears and select Reset to reset your API token. A confirmation appears in the top right of the screen.
- Select the copy button next to the API Token to copy the token to your system clipboard.
S2S endpoints
Endpoint | Function |
---|---|
https://s2s.adjust.com/event | Notifies Adjust of in-app events |
https://s2s.adjust.com/ad_revenue | Notifies Adjust of ad revenue data |
https://s2s.adjust.com/session | Notifies Adjust of session data |
Device identifiers
The device identifiers accepted for S2S events are as follows:
Preferred identifiers
Name | Value |
---|---|
Raw IDFA (IOS only) | idfa |
Raw Google advertising ID | gps_adid |
Raw Amazon Fire advertising ID | fire_adid |
Open Advertising ID (OAID, Huawei only) | oaid |
Web ID (Generated by the Adjust Web SDK) | web_uuid |
Backup identifiers
Name | Value |
---|---|
Raw IDFV (IOS only) | idfv |
Android ID (Android only) | android_id |
Event submission responses
All successfully recorded events return an OK
response.
Failed events return an HTTP error code and JSON message.
{ "error": "Event request failed (${error_message})" }
Error messages define the request problem. Use this table to identify your error, then review your setup or reach out to support@adjust.com for help.
Error code | Error message | Reason |
---|---|---|
400 | Bad event state | Occurs if request details don’t meet expectations. For example: created at time is before installed_at time. |
400 | Invalid app token | App token not set correctly |
400 | Ignoring event, earlier unique event tracked | A unique event was already recorded. This is ignored as a duplicate. |
400 | Invalid callback parameters | Callback parameters couldn’t be extracted |
400 | Invalid event token | Event token doesn’t exist, was set incorrectly, or doesn’t match the app token. |
400 | Invalid revenue | Amount set incorrectly or value too high (limit = 100,000,000,000) |
401 | Failed to authorize request | Authorization token missing or doesn’t match |
403 | App is inactive | App was deactivated in the dashboard |
403 | Tracking disabled | Measurement not enabled for this platform |
403 | Event token blocklisted | Event token blocklisted |
404 | App token not found | App token not found |
404 | Device not found | No device data found |
413 | Request size too large | Your request exceeds the limit of 1 MB |
451 | Device is opted out | Device is opted out |
500 | Internal error, contact support@adjust.com | Internal error when updating device data |