Errors
- 31 Dec 2023
- 1 Minute to read
- DarkLight
Errors
- Updated on 31 Dec 2023
- 1 Minute to read
- DarkLight
Article Summary
Share feedback
Thanks for sharing your feedback!
Sometimes your API request will generate an error 🤬 . Errors are no fun, especially when the error message isn't helpful. We wrote clear and helpful error messages for you but wanted to provide a bit more information to help you understand what went wrong and how you can fix it.
| Status code | Description |
|---|---|
302 - Redirect | The bearer token expired. You need to generate a new bearer token. |
401 - Unauthorized | The request couldn't be authenticated because the provided bearer token was not valid. If you receive this error more than once, we suggest you create a new API key and generate a new bearer token. |
403 - Forbidden | The role of the user that created the API key doesn't have permission to perform the action on the resource. the API key inherits the permissions of the role of the user that create the key. |
404 - Not found | The resource does not exist. It was either deleted or never existed. |
409 - Conflict | Returned when you make a Create a secret request and a secret with that name already exists. |
502 - Bad gateway | Something went wrong on Torq's side. |
Was this article helpful?