Reverse a close
Reverses one committed close: the credits it burned are returned and the coverage it wrote is cancelled. This is the amendment path for a close that priced the wrong work, which the client cannot restate because the request carries no amount.
The correction has two halves. This call undoes the credit side; to correct what was metered, re-send the same event unique_ids to POST /beta/events with corrected properties, then close again under a new Idempotency-Key. Doing only one half leaves the ledger and the invoice disagreeing.
Idempotent per close: voiding twice returns replayed: true and moves nothing. A voided close can never be replayed.
Authorizations
API key authentication. Pass your API key as a Bearer token.
Headers
2026-04-01 A unique string used to ensure the request is processed exactly once. If you retry a request with the same idempotency key within 24 hours, the original response is returned without re-executing the operation.
255"ik_a1b2c3d4e5f6"
Path Parameters
Unique identifier for the reservation
Body
Which close to reverse — a reservation settled in instalments has several, and only this distinguishes them. Send either the Idempotency-Key the close was sent with, or the close_key reported for it by the reservation read. A close sent without an Idempotency-Key has no other name, so the reservation read is the only way to identify it.
"close_run_88f_final"
Response
Success