Shure — Troubleshooting

📘
Related setup guide
Setting up Shure? See the Shure connector setup guide.

Error message	Likely meaning (TL;DR)	Recommended next steps
Unauthorized	ShureCloud rejected the connector's Client ID and Client Secret. The secret was regenerated or revoked, the integration was removed in ShureCloud, or the values were copied incorrectly.	In ShureCloud, go to Organization Settings → ShureCloud API and confirm the integration still exists. Copy its Client ID, reveal or regenerate the Client Secret, and paste both into the Shure connector's API Configuration screen in Xyte. Then save. If the credentials are correct and it still fails, check for a ShureCloud service announcement and try again later.
Insufficient privileges for Shure.	ShureCloud accepted the credentials but refused access: API access is not enabled for the organization, or the integration has no access to these devices.	In ShureCloud, open Organization Settings → ShureCloud API and confirm API access is enabled and the integration is still listed. If it was changed, create a new integration and enter its Client ID and Client Secret in the connector.
Shure: 429 Rate Limit Exceeded	ShureCloud's API limit was reached. ShureCloud allows a fixed number of API requests per organization each month, and also limits short bursts of requests.	No change to the connector is needed. A short-term limit clears on its own within minutes. If the monthly allowance is used up, ShureCloud blocks requests until it resets at the start of the next calendar month (UTC), and syncing resumes after that.

Error message

Likely meaning (TL;DR)

Recommended next steps

Unauthorized

ShureCloud rejected the connector's Client ID and Client Secret. The secret was regenerated or revoked, the integration was removed in ShureCloud, or the values were copied incorrectly.

In ShureCloud, go to Organization Settings → ShureCloud API and confirm the integration still exists.

Copy its Client ID, reveal or regenerate the Client Secret, and paste both into the Shure connector's API Configuration screen in Xyte. Then save.

If the credentials are correct and it still fails, check for a ShureCloud service announcement and try again later.

Insufficient privileges for Shure.

ShureCloud accepted the credentials but refused access: API access is not enabled for the organization, or the integration has no access to these devices.

In ShureCloud, open Organization Settings → ShureCloud API and confirm API access is enabled and the integration is still listed.

If it was changed, create a new integration and enter its Client ID and Client Secret in the connector.

Shure: 429 Rate Limit Exceeded

ShureCloud's API limit was reached. ShureCloud allows a fixed number of API requests per organization each month, and also limits short bursts of requests.

No change to the connector is needed. A short-term limit clears on its own within minutes.

If the monthly allowance is used up, ShureCloud blocks requests until it resets at the start of the next calendar month (UTC), and syncing resumes after that.