Most API errors are straightforward — a missing header, a wrong API key, an invalid field value. The Error Codes Reference covers those. This page explains the less obvious case: how to interpret error responses when something unexpected happens inside the system.
Every Doctavian error response includes two fields that tell you where the error came from and how far the request got before it failed:
| Field | Description |
|---|---|
eventId | Identifies where in the system the error was logged. Points to the specific location in the codebase where the failure was caught. |
operationId | End-to-end context ID that traces the full request through the system. Present on every response, successful or not. |
When eventId is missing from the response, the error was an unexpected exception — something the system did not anticipate. This is distinct from a standard error response where eventId is present and the failure was caught and handled.
In this case, only operationId is available. Include it when contacting support so the team can trace the full request through the system, even without a specific log anchor point.
An unhandled error that recurs consistently is worth reporting immediately — it likely indicates a bug rather than a configuration issue.
Always include the following in your support request:
operationId and eventId if presentReach out via support.doctavian.com.