Error Reference & Status Codes
Comprehensive guide to HTTP status codes, internal Aevum Zenth error identifiers, API response structures, and division-specific fault codes.
The server cannot process the request due to malformed syntax, invalid parameters, or missing required fields in the payload.
Authentication credentials are missing, expired, or invalid. Requires valid Bearer token or API key in the Authorization header.
The request is valid, but the server refuses to authorize it due to insufficient permissions, IP restrictions, or policy violations.
The requested resource could not be found on the server. Verify endpoint paths, resource IDs, and API version parameters.
Rate limit exceeded. Review `X-RateLimit-Reset` header and implement exponential backoff. Enterprise tiers allow burst quotas.
An unexpected condition was encountered on the server. Check `X-Trace-Id` for logs. Contact Aevum Zenth engineering if persistent.
JWT signature mismatch, expired token, or invalid issuer claim. Token must be refreshed via `POST /auth/token/refresh`.
Target microservice instance unavailable or connection pool saturated. Retry with jitter. Scale request routed to fallback region.
Internal service mesh failed to respond within SLA window. Check service mesh dashboard. Automatic circuit breaker engaged.
Aerospace division telemetry stream contains invalid JSON structure or missing epoch timestamps. Validate against schema v4.2.
Healthcare division request lacks required consent flags or BAA association. Patient data masked. Contact compliance@zenth.aevum
Energy division grid synchronization timeout. Load balancer detached node. Fallback routing active. ETA resolution: 12m.
Standard API Error Response Format
All Aevum Zenth API endpoints return errors in a consistent JSON structure. The `trace_id` is required for support tickets and log correlation.
{
"status": 500,
"error_code": "AZ-SYS-500",
"message": "Internal server error encountered",
"details": {
"trace_id": "az-trace-8f9a2b3c4d5e6f7g",
"timestamp": "2026-01-15T08:42:11Z",
"documentation_url": "https://docs.zenth.aevum/error-reference"
},
"retry_after": null
}
Headers are also injected for debugging: `X-Trace-Id`, `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Reset`.
Need Help Resolving an Error?
Our engineering support team monitors error patterns and can assist with custom integrations and rate limit adjustments.
Open Support TicketSystem Status & SLAs
Real-time uptime metrics, incident reports, and maintenance windows for all Aevum Zenth cloud infrastructure.
View Status PageDivision-Specific Documentation
Deep-dive guides for Aerospace telemetry, Healthcare compliance schemas, and Energy grid protocols.
Browse Division Docs