In Acoustic Exchange, users select endpoints to add to their working environment by registering endpoints with Acoustic Exchange. On the Endpoints tab, Acoustic Exchange provides a wizard to guide users through the registration process.
The endpoint registration wizard lists and describes the endpoints that are available for registration. The wizard lists your solution as an available endpoint if you provision your endpoint by creating an Acoustic Exchange application in the Acoustic Exchange Integration Manager during the partner provisioning and approval process. In the Integration Manager, you describe the endpoint, indicate where it is deployed, and specify how Acoustic Exchange users submit access credentials during endpoint registration.
The wizard presents users with two ways to provide their access credentials.
- Instructions only. Users contact you to submit the credentials by following instructions that you provide to Acoustic Exchange. The registration wizard displays the exact instructions that you provide in the API call.
- Direct connect. Users enter credentials directly through the endpoint wizard. The wizard displays entry fields based on properties that you specify in the call to the onboarding API.
During the registration process, Acoustic Exchange generates an authentication key in response to the user request. The method that is used to generate the key depends on how you integrate with Acoustic Exchange during partner provisioning.
Acoustic Exchange recognizes the key as authorization to allow actions by you on behalf of the Acoustic Exchange user. Your solution appears to the Acoustic Exchange user as Pending until you and Acoustic Exchange complete the endpoint registration process. When endpoint registration is complete, your endpoint appears on the Endpoint tab as Active and Acoustic Exchange users can begin to use your solution to address their business needs thorough Acoustic Exchange.
If you do not use the Integration Manager to integrate with Acoustic Exchange, users must register your endpoint as a custom endpoint. Registering a custom endpoint requires that the Acoustic Exchange user manually generate an authentication key and submit the key to you. You must provide the means for users to submit the key and you must contact the Acoustic Exchange account provisioning team to create and maintain a separate endpoint for each user account.