Submit a resolution outcome for an instrument (reporter only).
POST/v1/instrument/resolution/submit
Reporters submit the binary outcome (YES/NO) for an instrument in the pending
lifecycle state. V0 is operator-attested with a single reporter key; V1 introduces
reporter quorum and a dispute window.
Authentication is via the X-Reporter-Key header (distinct from customer Bearer
tokens).
Request
Responses
- 200
- 400
- 403
- 503
Resolution recorded; instrument advances to FINAL.
Request was malformed or failed validation. The error.code field carries the
machine-readable reason; common values include invalid_request, invalid_json,
invalid_order_id, invalid_instrument_id, invalid_credential_id,
invalid_resolution, and operation-specific codes documented per endpoint.
Authentication succeeded but the action is not permitted.
A required downstream (matching engine, ClickHouse, custody, instrument service) is unreachable. The request was not processed; retry with backoff.