Responses

BigPanda uses conventional HTTP response codes to indicate the success or failure of a request. A 2xx code means success, a 4xx code means the request was rejected, and a 5xx code means a server-side problem.

Response codes

Code	Meaning
`200 OK`	Success.
`201 Created`	Resource created.
`202 Accepted`	Request accepted for asynchronous processing. Check the Job resource for results.
`204 No Content`	Success with no response body.
`400 Bad Request`	Missing or invalid parameter. Check the error message and your payload.
`401 Unauthorized`	Token is invalid or missing. Check the `Authorization` header.
`403 Forbidden`	Token is valid but lacks the required permission.
`404 Not Found`	The endpoint or resource does not exist.
`409 Conflict`	Request conflicts with the current state, for example resolving an already-resolved incident.
`410 Gone`	The resource has been removed permanently.
`429 Too Many Requests`	Rate limit exceeded. Retry after the interval indicated in the response.
`500 Internal Server Error`	Server-side issue. Retry after a short wait.
`501 Not Implemented`	The endpoint does not support that method.

Success responses

A successful GET returns the requested resource or a list of resources as JSON. A successful POST or PUT returns the created or updated resource, or 204 No Content when there is no body to return. Long-running requests return 202 Accepted; see Asynchronous operations for details.

Error responses

When a request fails, BigPanda returns a non-2xx code and, where applicable, a JSON body describing the error.

For specific response codes and errors per endpoint, see each endpoint in the API reference.

Next steps

Errors and troubleshooting: Map common codes to causes and fixes.

Pagination: Read paginated list responses.

Best practices: Handle retries and rate limits.

Response codes#

Success responses#

Error responses#

Next steps#

Response codes

Success responses

Error responses

Next steps