Health Gorilla uses standard HTTP status codes to indicate the outcome of every API request. Errors are accompanied by a FHIR OperationOutcome resource that provides detailed diagnostics in a machine-readable format.

This page lists the most common status codes returned by the Health Gorilla API and explains how to interpret them.

Success Codes

Status Code	Meaning	Description
`200 OK`	Success	The request was successful and a response body is returned.
`201 Created`	Resource created	A new FHIR resource was successfully created.
`202 Accepted`	Request accepted (async)	The request was accepted for processing (e.g., `$p360-retrieve`).
`204 No Content`	Success with no body	The operation succeeded but no response body is returned.

Client Errors

Status Code	Meaning	Typical Cause
`400 Bad Request`	Malformed or invalid input	Missing fields, wrong types, or invalid values.
`401 Unauthorized`	Authentication failed	Missing, expired, or invalid access token.
`403 Forbidden`	Insufficient permissions	Valid token, but lacking required scope or role.
`404 Not Found`	Resource not found	The specified resource does not exist.
`409 Conflict`	Duplicate or conflicting data	Resource already exists or cannot be updated due to conflict.
`422 Unprocessable Entity`	Validation failed	Semantically correct request, but FHIR validation failed.

Server Errors

Status Code	Meaning	Typical Cause
`500 Internal Server Error`	Server error	Unexpected system error — try again later.
`503 Service Unavailable`	Maintenance or overload	The system is temporarily unavailable.

All error responses include a FHIR OperationOutcome resource with structured details.