Fix API authorization errors (401 or 403) due to missing system permissions in Snow Atlas
When you receive 401(Unauthorized) or 403(Forbidden) errors when calling Snow Atlas APIs, the issue may be due to missing system permissions within Snow Atlas. Including scopes in the token request alone is not sufficient; corresponding System permissions must be explicitly enabled.
The following errors may be observed:
• 403 Forbidden, indicating a required scope is missing from the token when accessing Inventory APIs.
• 401 Unauthorized, indicating that the token is invalid or inactive when accessing Custom Fields APIs.
This commonly happens when required permissions are not enabled in the Application Registration. Even if scopes are included in the token request and access tokens are generated, Snow Atlas checks system-level permissions before allowing access. Authorization errors such as 401 or 403 should first be validated against Application Registration permissions before troubleshooting token format or request headers.
Following the steps below helps you identify and access missing permissions, so your Snow Atlas API calls are successful.
Grant required system permissions
- Go to Snow Atlas > Settings > Application Registrations.
- Select the application registration you’re using.
- Select Edit application registration.
- Open the Permissions section.
- Go to the System tab.
- Enable the permissions required for your API, for example:
- Inventory APIs
- Custom fields APIs
- Select Save.
- Generate a new access token.
- Retry your API request.
If the issue was caused by missing system permissions, the API request should succeed after generating a new access token.
