Errors and Troubleshooting

When a request fails, the HTTP response code tells you what went wrong. Use the table below to map a common code to its likely cause and fix. For the full list of codes, see Responses.

Common errors

Code	Likely cause	What to do
`400 Bad Request`	A required field is missing or a value is invalid.	Read the error message and check your payload against the endpoint reference.
`401 Unauthorized`	The token is missing, malformed, or invalid.	Confirm the `Authorization` header is set to `Bearer <your_api_key>` and the key is active.
`403 Forbidden`	The token is valid but the user's role lacks the permission.	Ask an administrator to grant the required role permission. See the Roles Management documentation.
`404 Not Found`	The endpoint path or resource ID is wrong, or you are calling the wrong region.	Verify the path, the resource ID, and your base URL. See Regions and base URLs.
`409 Conflict`	The request conflicts with the current state, for example resolving an already-resolved incident.	Check the current state of the resource before retrying.
`429 Too Many Requests`	You exceeded the endpoint's rate limit.	Retry after the interval in the response, using exponential backoff. See Best practices.
`500 Internal Server Error`	A server-side problem.	Retry after a short wait. If it persists, contact Support.

Diagnose integration delivery

If alerts or data are not arriving as expected, pull troubleshooting logs for the affected integration using the Troubleshooting logs endpoints in the API reference. The logs show delivery failures, parsing errors, and upstream issues.

Get help

If you cannot resolve an issue, contact BigPanda Support.

Next steps

Responses: See the full response code list.

Best practices: Build in retries and backoff.

Authentication and headers: Fix auth errors.

Common errors#

Diagnose integration delivery#

Get help#

Next steps#

Common errors

Diagnose integration delivery

Get help

Next steps