1 min read
Interpret API authentication, permission and rate-limit failures
Review the cause before repeating requests.
Before you start
- Use an account-authorized integration and have the appropriate credential.
Step by step
Read the HTTP status and returned message.
For an invalid credential, check the key and whether it was regenerated; for denied access, check the account, resource and required permission.
If rate-limited, respect the Retry-After duration before retrying.
For support, provide the time, method, path and message while removing credentials and unnecessary personal data.
Check your result
You gather the information needed to resolve or report the failure.
What you need to know
- A valid key does not remove ownership, module, plan or resource-state rules.
- Do not automatically repeat a write after an uncertain response without checking whether the operation already happened.