fulfillments

Create Fulfillment (service, on behalf of a payee)

Service-key only (X-API-Key must be a service key this route trusts; today enforcer-mp-merchant and enforcer-airdrop). Creates an OPEN payment request that pays payee_account_id: the payee is creator, sender and receiver, and the use case opens it to any same-tenant payer. The body cannot name a different payer or creator. Tenant is X-Tenant-ID; the payee must belong to it.

post/service/fulfillments

Request

  • Base URL: https://api.instruxi.dev/api/v1/enforcer
  • URL: https://api.instruxi.dev/api/v1/enforcer/service/fulfillments
  • Auth: none declared. Required headers: X-Tenant-ID

Headers

X-Tenant-IDstring required

tenant id

Request body

chain_idinteger
deadlinestring

RFC3339

idempotency_keystring

IdempotencyKey, as on POST /fulfillments. A service has no /me list to recover a lost create through, so this is how a retry finds the original.

notional_uoastring
payee_account_idstring

PayeeAccountID is the account this request pays: creator, sender and receiver all at once. Required.

receiver_walletstring
referencestring
refund_walletstring

RefundWallet redirects any refund of this sale to a platform wallet (a partner-API sale is settled with the partner's users off-chain, so the on-chain payer is not who is owed). Only the services in ServiceFulfillmentRefundWalletCallers may set it.

request_tokenstring

Response

Created

successboolean

Example response

{
  "success": true
}

Changes

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