Overview

Authorization to ShureCloud is done via API client credentials (a Client ID and Client Secret) generated for an application with access to the devices to be monitored.

API Access Requirements

To use the ShureCloud REST API with Xyte, make sure you have:

• Required account / tenant: ShureCloud organization, accessed with a My Shure ID
• Required access: API access enabled for your organization, with permission to create API applications
• Required plan / license: Depends on your ShureCloud deployment and entitlements
• Where to verify: ShureCloud organization / API settings

Get your API credentials

Xyte connects to ShureCloud using a Client ID and Client Secret. Generate them in ShureCloud (sign in with a My Shure ID that can manage API access, create or select an API application for your organization), then paste the application's Client ID and Client Secret into the matching fields shown above.

For detailed instructions, visit the Shure REST API documentation.

These credentials are stored securely on Xyte servers and are used only to authenticate with ShureCloud on your behalf.

Notes

• Store the Client Secret when it is first shown. Many platforms display the secret only once at creation; if it is lost, you must reset/regenerate it (which invalidates the old secret).
• If 2FA or SSO restrictions are enabled on your ShureCloud account, use a dedicated API application rather than personal login credentials, or coordinate with your Xyte representative.

Additional information

Connector root space name: Shure 2

If deleted and re-added:

⚠️

Deleting this connector will remove all imported devices and their data. This action cannot be undone.

• A new connector will be created upon re-adding.
• If the name ShureCloud already exists, the new connector will be named ShureCloud 1.
• The device tree will be re-imported under the new connector.
• The tree hierarchy will not be deleted.