HTTP guides
Errors and retry behavior
Treat contract failures, authorization, and uncertain delivery separately.
The OpenAPI operation pages include response statuses and ErrorResponse. Preserve the server's machine-readable error and message; do not convert every failure into an empty result.
Client handling
| Failure class | Client response |
|---|---|
| Invalid payload or query | Correct the contract violation before retrying. |
| Missing/expired session | Re-authenticate; do not reuse an invalid token indefinitely. |
| Missing capability or trust | Request appropriate operator provisioning; signing again does not grant authority. |
| Idempotency conflict | Inspect the original request; never mutate payload under the same key. |
| Stale transfer or cursor | Read current state and begin a new deliberate operation/query. |
| Uncertain network delivery | Retry the identical mutation with its original idempotency key. |
Avoid retry storms. Use bounded backoff where a retry is appropriate and respect server limits. A rejected protected mutation is not a successful registry write.
Source authority
This page describes the checked-in implementation, not the availability of a public registry.
mars-server/src/api/mod.rsmars-server/src/contracts.rsdocs/api/openapi.v1.json