fulfillments

Record the tx hashes sent for a reserved settle/refund (system admin)

The settle worker's second step after mode=reserve: stores the hashes on the (intent, kind) reservation and moves the intent (settle -> settling, refund -> refunded). Sends nothing. 409 action_already_completed when the reservation already has a tx hash; 409 no_reservation when there is none.

post/admin/mpp-deposit-intents/{id}/complete

Request

  • Base URL: https://api.instruxi.dev/api/v1/enforcer
  • URL: https://api.instruxi.dev/api/v1/enforcer/admin/mpp-deposit-intents/{id}/complete
  • Auth: API key in header Authorization

Path parameters

idstring required

intent id

Request body

kind'settle' | 'refund'
tx_hashesstring[]

Response

OK

successboolean

Changes

No recorded changes to this operation across all 1 revision of this API.