API Error Handling
This page provides a public summary of API error-handling expectations.
Basic concept
CO2 TRUST APIs use standard HTTP status behavior and structured error responses. Integration teams should implement robust retry, logging, and alerting behavior based on endpoint-specific guidance in code docs.
For technical implementation details
Use:
Public guidance
- Client-side errors generally indicate invalid input or missing/insufficient authorization.
- Server-side errors generally indicate transient or service-level failures.
- Production integrations should include retries for transient failure classes and clear user-facing error messaging.