Errors

The canonical external error envelope and status-code matrix are forthcoming. Endpoint documentation will define expected failures alongside each operation.

​

Client behavior

Until a specific contract is published, integration clients should follow conservative HTTP practices:

• treat only documented outcomes as success;
• set explicit timeouts;
• retry only operations documented as safe to retry;
• use bounded exponential backoff with jitter;
• avoid logging credentials or sensitive payloads;
• retain correlation metadata returned by Atlas;
• surface validation and permission failures to an operator.

​

Failure categories

Plan for authentication or authorization, validation, not found, conflict, rate limit, and internal error categories. The exact status codes and response fields will be documented with the API reference.