Overview
If every request you send to the Signal Genesys External API returns an HTTP 403 – Invalid scope provided error, your API token may be missing one or more required permission scopes. This article explains what causes the error and what to have ready when contacting our team to resolve it.
What Causes the 403 'Invalid Scope' Error?
A 403 scope error means your bearer token was authenticated successfully, but it does not have permission to perform the action you requested. Common reasons include:
- The token was generated without the necessary permission scopes for the External API feature you are trying to use.
- Your token was created with a limited scope configuration that excludes certain External API features.
- Your plan tier may not include External API access, so the platform blocks those scopes entirely.
- The token has expired or been rotated and the updated token was not saved in your integration.
What to Do
Because resolving a 403 scope error on the Signal Genesys External API requires backend verification of your token permissions and plan entitlements, our support team will need to investigate on your behalf. To help us resolve this as quickly as possible, please have the following ready before reaching out:
- Your Search Atlas account email address
- The exact 403 error message you are receiving
- The specific API endpoint or action you are attempting to call
- The date and time (with timezone) when the error first occurred
- Your current plan or subscription tier, if known
Do not share your full bearer token when contacting support — our team can look up your token configuration securely on the backend.
If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.