Read the stored result of a completed idempotency key
Answers whether a keyed mutation already committed, without running anything.
/v1/ledgers/{ledgerId}/idempotency/{key}Answers whether a keyed mutation already committed, without running anything. A caller whose own transaction died after the mutation committed here probes this before re-deriving anything from mutable state: found means the money already moved and the stored response is the truth to repair from. Not found is idempotency_key_not_found (404) and is authoritative within the 30-day retention window: the keyed mutation never committed. No request hash is compared, because a caller repairing after a crash may no longer be able to reproduce the request body it sent.
Authorization
bearerAuth In: header
Path Parameters
uuid1 <= length <= 255Response Body
application/json
application/problem+json
curl -X GET "https://example.com/v1/ledgers/497f6eca-6276-4993-bfeb-53cbbbba6f08/idempotency/string"{ "status_code": 0, "response": null}Page the event feed ascending from a (xact, seq) cursor
Events are served in (xact, seq) order and only once every transaction older than theirs has finished, so a consumer that stores the last event's (xact, seq) as its cursor sees every event exactly...
Liveness probe
Liveness only. The handler answers as soon as the process is serving and touches neither the database nor any consumer state, so a degraded dependency does not take the container down.