400 Client Error
Bad Request

The server cannot process the request due to malformed syntax, invalid parameters, or missing required fields in the payload.

401 Security
Unauthorized

Authentication credentials are missing, expired, or invalid. Requires valid Bearer token or API key in the Authorization header.

403 Security
Forbidden

The request is valid, but the server refuses to authorize it due to insufficient permissions, IP restrictions, or policy violations.

404 Client Error
Not Found

The requested resource could not be found on the server. Verify endpoint paths, resource IDs, and API version parameters.

429 Rate Limit
Too Many Requests

Rate limit exceeded. Review `X-RateLimit-Reset` header and implement exponential backoff. Enterprise tiers allow burst quotas.

500 Server Error
Internal Server Error

An unexpected condition was encountered on the server. Check `X-Trace-Id` for logs. Contact Aevum Zenth engineering if persistent.

AZ-ERR-001 Security
Token Validation Failed

JWT signature mismatch, expired token, or invalid issuer claim. Token must be refreshed via `POST /auth/token/refresh`.

AZ-SYS-404 System
Resource Pool Exhausted

Target microservice instance unavailable or connection pool saturated. Retry with jitter. Scale request routed to fallback region.

AZ-NET-503 Network
Upstream Gateway Timeout

Internal service mesh failed to respond within SLA window. Check service mesh dashboard. Automatic circuit breaker engaged.

AERO-TEL-422 Division
Telemetry Payload Malformed

Aerospace division telemetry stream contains invalid JSON structure or missing epoch timestamps. Validate against schema v4.2.

HLTH-PRIV-403 Division
HIPAA/GDPR Access Denied

Healthcare division request lacks required consent flags or BAA association. Patient data masked. Contact compliance@zenth.aevum

ENRG-GRID-503 Division
Smart Grid Sync Failure

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 Ticket

System Status & SLAs

Real-time uptime metrics, incident reports, and maintenance windows for all Aevum Zenth cloud infrastructure.

View Status Page

Division-Specific Documentation

Deep-dive guides for Aerospace telemetry, Healthcare compliance schemas, and Energy grid protocols.

Browse Division Docs