Home/Docs
Diagnostics
Structured error envelopes
Every RC Lite HTTPS response uses the same disciplined envelope pattern as mainstream REST APIs: deterministic code, human message, retryable guidance, propagated requestId, optional details, plus deep-linked docsUrl anchors (mirrored below for offline quoting).
The request lacks an RC Lite credential header.
Retry guidance: Fix payload/root cause first
- Invalid API key [invalid_api_key]
The presented key is missing, malformed, or not recognized for this environment.
Retry guidance: Fix payload/root cause first
- API key revoked [api_key_revoked]
The key was revoked, rotated, or explicitly disabled.
Retry guidance: Fix payload/root cause first
- Rate limited [rate_limited]
Tenant or key exceeded plan RPM/burst windows. Honor Retry-After headers.
Retry guidance: Eligible for exponential backoff retries
- Idempotency key required [idempotency_required]
POST/PUT/PATCH to this route requires an Idempotency-Key header to prevent duplicate CAD/billing writes.
Retry guidance: Fix payload/root cause first
- Idempotency conflict [idempotency_conflict]
The same Idempotency-Key was reused with different payload fingerprints.
Retry guidance: Fix payload/root cause first
- CAD export mapping failed [cad_export_mapping_failed]
The incident payload could not be mapped onto the nominated CAD adapter schema.
Retry guidance: Fix payload/root cause first
- Not implemented [not_implemented]
The route exists but upstream processing is still being provisioned.
Retry guidance: Eligible for exponential backoff retries
Operational teams may expand this catalogue with CAD adapter-specific codes (prefixed CAD_EXPORT_*) — keep machine-readable enums synchronized with Dynamo audit exports.