### [S2S endpoints](s2s-endpoints)

<table>
  <thead>
    <tr>
      <th>Endpoint</th>
      <th>Use</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td><code>https://s2s.adjust.com/event</code></td>
      <td>Notifies Adjust of in-app events</td>
    </tr>
    <tr>
      <td><code>https://s2s.adjust.com/ad_revenue</code></td>
      <td>Notifies Adjust of ad revenue data</td>
    </tr>
  </tbody>
</table>

### [Accepted device identifiers](accepted-identifiers)

The device identifiers accepted for S2S events are as follows:

<table>
  <thead>
    <tr>
      <th colspan="2">Preferred identifiers</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Raw IDFA (IOS only)</td>
      <td><code>idfa</code></td>
    </tr>
    <tr>
      <td>Raw Google advertising ID</td>
      <td><code>gps_adid</code></td>
    </tr>
    <tr>
      <td>Raw Amazon Fire advertising ID</td>
      <td><code>fire_adid</code></td>
    </tr>
    <tr>
      <td>Open Advertising ID (OAID, Huawei only)</td>
      <td><code>oaid</code></td>
    </tr>
    <tr>
      <td>Web ID (Generated by the Adjust Web SDK)</td>
      <td><code>web_uuid</code></td>
    </tr>
  </tbody>
</table>

<table>
  <thead>
    <tr>
      <th colspan="2">Backup identifiers</th>
    </tr>
  </thead>
  <tbody>
    <tr>
      <td>Raw IDFV</td>
      <td><code>idfv</code></td>
    </tr>
    <tr>
      <td>Android ID</td>
      <td><code>android_id</code></td>
    </tr>
  </tbody>
</table>


## [Event submission responses](event-submission-responses)

All successfully tracked events return an `OK` response.

Failed events return an HTTP error code and JSON message, like this: `{"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.

<table border="1">
  <tbody>
    <tr>
      <td><b>Error code</b></td>
      <td><b>Error message</b></td>
      <td><b>Reason</b></td>
    </tr>
    <tr>
      <td>400</td>
      <td>Bad event state</td>
      <td>Can occur for various reasons. E.g., ‘created at’ time is before 'installed_at' time.<p dir="ltr">Check the response for additional details.</p>
      </td>
    </tr>
    <tr>
      <td>400</td>
      <td>Invalid app token</td>
      <td>App token not set correctly</td>
    </tr>
    <tr>
      <td>400</td>
      <td>Ignoring event, earlier unique event tracked</td>
      <td>A unique event was already tracked. This is ignored as a duplicate.</td>
    </tr>
    <tr>
      <td>400</td>
      <td>Invalid callback parameters</td>
      <td>Callback parameters could not be extracted</td>
    </tr>
    <tr>
      <td>400</td>
      <td>Invalid event token</td>
      <td>Event token does not exist, was set incorrectly, or does not match the app token.</td>
    </tr>
    <tr>
      <td>400</td>
      <td>Invalid revenue</td>
      <td>Amount set incorrectly or value too high (limit = 100,000,000,000)&nbsp;</td>
    </tr>
    <tr>
      <td>401</td>
      <td>Failed to authorize request</td>
      <td>Authorization token missing or does not match</td>
    </tr>
    <tr>
      <td>403</td>
      <td>App is inactive</td>
      <td>App was deactivated in the dashboard</td>
    </tr>
    <tr>
      <td>403</td>
      <td>Tracking disabled</td>
      <td>Tracking not enabled for this platform</td>
    </tr>
    <tr>
      <td>403</td>
      <td class="notranslate">Event token blocklisted</td>
      <td>Event token blocklisted</td>
    </tr>
    <tr>
      <td>404</td>
      <td class="notranslate">App token not found</td>
      <td>App token not found</td>
    </tr>
    <tr>
      <td>404</td>
      <td>Device not found</td>
      <td>No device data found</td>
    </tr>
    <tr>
      <td>413</td>
      <td>Request size too large</td>
      <td>Your request exceeds our limit of 1 MB</td>
    </tr>
    <tr>
      <td>451</td>
      <td>Device is opted out</td>
      <td>Device is opted out&nbsp;</td>
    </tr>
    <tr>
      <td>500</td>
      <td>Internal error, contact support@adjust.com</td>
      <td>Internal error when updating device data</td>
    </tr>
  </tbody>
</table>


S2S API reference

Take your growth to the next level with Adjust’s setup guides, best practices, and FAQs.

Marketer

Integrate our APIs and open-source SDKs with your apps and business analytics.


Developer

In-depth advice for our global Technology Partners on how best to work with Adjust.


Endpoint	Use
`https://s2s.adjust.com/event`	Notifies Adjust of in-app events
`https://s2s.adjust.com/ad_revenue`	Notifies Adjust of ad revenue data

Preferred identifiers
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`

Error code	Error message	Reason
400	Bad event state	Can occur for various reasons. E.g., ‘created at’ time is before 'installed_at' time. Check the response for additional details.
400	Invalid app token	App token not set correctly
400	Ignoring event, earlier unique event tracked	A unique event was already tracked. This is ignored as a duplicate.
400	Invalid callback parameters	Callback parameters could not be extracted
400	Invalid event token	Event token does not exist, was set incorrectly, or does not 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 does not match
403	App is inactive	App was deactivated in the dashboard
403	Tracking disabled	Tracking 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 our 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

Backup identifiers
Raw IDFV	`idfv`
Android ID	`android_id`