Business solutions from Acoustic ecosystem partners can integrate with Acoustic Exchange only after the solution provider completes an account provisioning process. The process includes implementation of Acoustic Exchange public APIs, and solution testing in the Acoustic Exchange Pilot environment, and Acoustic review and approval of the solution as a Acoustic Exchange endpoint.

Note: Applications are provisioned internally by the Acoustic Exchange Provisioning team.

For Acoustic ecosystem business partners, integrating with Acoustic Exchange proceeds as follows.

1. Email exchange-partnership@acoustic.com with the Subject line: Partner Pilot Account Request.
2. As an Acoustic Business Partner, you must validate that your business solution is compatible with Acoustic Exchange and uses Acoustic Exchange to share event or audience data with at least one Acoustic product. Complete the following steps:
   • Submit and nominate your solution as a candidate for integration with Acoustic Exchange as an endpoint provider.
   • Complete a solution review, including a demonstration to Acoustic. You must access the Acoustic Exchange Pilot environment to complete this step.
   • Receive the Ready for Acoustic mark and sign the associated license agreement.
3. To begin the solution review process, implement Acoustic Exchange public APIs and test your solution in the Acoustic Exchange Pilot environment with the Acoustic Exchange Integration Manager. You can access the Integration Manager through the navigation menu in Acoustic Exchange. It guides you through the implementation process where you describe your Acoustic Exchange application, the types of data that you support, and how you make yourself available to Acoustic business users. For more information, review the Integration Manager documentation.

   Acoustic must give you the access credentials and base URL for API calls to the Pilot environment. The Acoustic Exchange Provisioning Team sends the access credentials in a series of email messages to a contact that you must designate.

4. Create a user interface or business process that enables Acoustic users to register your endpoint for their Acoustic Exchange user account.
5. Upon completion of the solution review in the Pilot environment, demonstrate the candidate endpoint to Acoustic.

   Acoustic must approve your solution as a Acoustic Exchange endpoint and authorize promotion from the Acoustic Exchange Pilot environment to the Acoustic Production environment. After Acoustic approves your Acoustic Exchange application, the Acoustic team promotes your application to the Acoustic Exchange Production environment. You can then publish your application in Production to make your endpoint visible to users.

After Acoustic promotes your endpoint to Acoustic Exchange Production, when you receive a registration request and an authentication key from a Acoustic Exchange user, you can register as a Acoustic Exchange endpoint on behalf of that Acoustic Exchange user account. Doing so enables the Acoustic Exchange user to syndicate event or audience data that your business solution produces or consumes. 

Acoustic Exchange partners include Acoustic product teams and product teams from Acoustic Exchange Business Partners whose products are enabled for Acoustic Exchange.

When a product is fully integrated with Acoustic Exchange, it becomes available to marketers in the Acoustic Exchange user interface as an endpoint. Marketers begin to use the product in Acoustic Exchange by registering the endpoint in their Acoustic Exchange user account. Marketers can then use Acoustic Exchange to solve various business problems by exchanging data between multiple registered endpoints. No custom software integration is required. However, the marketers must be valid users of the product that they register as an Acoustic Exchange endpoint.

Note: Integration with Acoustic Exchange for companies outside of Acoustic Exchange requires that the company first become a certified Acoustic Exchange Business Partner. Becoming certified as an Acoustic Exchange Business Partner requires actions that are separate from the Acoustic Exchange integration process.