Acoustic Exchange provides a collection of public REST APIs that endpoints call to connect to Acoustic Exchange as producers and consumers of event and audience data.

The APIs include various properties to provide customer identifiers and event attributes as part of the API call.

Acoustic Exchange endpoints call the Acoustic Exchange public APIs over SSL.

Calls to Acoustic Exchange public APIs must contain a valid authentication key that Acoustic Exchange provides to users for each endpoint that they register. The authentication key identifies the Acoustic Exchange endpoint and a specific Acoustic Exchange user account that is associated with the endpoint.

All data exchanges through Acoustic Exchange occur on behalf of a specific Acoustic Exchange user and user account. Including an authentication key with each API call ensures that the data is directed to the correct destination and that customer identifiers are attributed to the correct Acoustic Exchange account. Acoustic Exchange does not share identifier data across Acoustic Exchange accounts.

The authentication key must appear in the HTTP header of the API call. Acoustic Exchange rejects any API call that does not specify an authentication key that Acoustic Exchange can associate with a valid Acoustic Exchange account.