fulfillment

Failed / all P2P fulfillments, tenant-wide (admin)

The CS failed-P2P dashboard: fulfillments across the tenant. Party scope is OPTIONAL: user_id matches EITHER side (sender, receiver or creator), while sender_user_id / receiver_user_id pin one end. All supplied filters intersect, so sender+receiver together mean "from A to B". Without them the list is tenant-wide and only pageable. status = closed (cancelled|declined|expired — the failed set), outstanding (pending|claimed|submitted), all, or an exact status. A system admin may pass ?tenant_id to view another tenant; tenant-scoped callers (tenant_admin, developer) are pinned to their own. total matches the rows' filter.

get/admin/fulfillments

Request

  • Base URL: https://api.instruxi.dev/api/v1/enforcer
  • URL: https://api.instruxi.dev/api/v1/enforcer/admin/fulfillments
  • Auth: one of:
    • API key in header Authorization
    • API key in header X-API-Key

Query parameters

statusstring

closed|outstanding|all|<exact> (default all)

sort'recent' | 'oldest'

recent (newest first, default) | oldest

tenant_idstring

view another tenant (admin only)

user_idstring

scope to one person on EITHER side (sender, receiver or creator)

sender_user_idstring

scope to transfers SENT by this user

receiver_user_idstring

scope to transfers RECEIVED by this user

reference_prefixstring

reference starts with this literal prefix (e.g. RWD:<group_id>:) — payout-campaign rows

group_idstring

sugar for reference_prefix=RWD:<group_id>: — everything fanned out from this payout group

kind'p2p' | 'deposit' | 'billpay' | 'direct' | 'reward' | 'terminal'

p2p (no machine tag — a real person-to-person transfer) | deposit (DEPOSIT:) | billpay (BP:) | direct (DIRECT:) | reward (RWD:) | terminal (TERMINAL: — a POS sale)

self_payments'include' | 'exclude' | 'only'

include (default) | exclude | only — sender == receiver rows (bill-pay funding, quick pays, self-sends)

created_afterstring

RFC3339 lower bound (inclusive)

created_beforestring

RFC3339 upper bound (exclusive)

tx_hashstring

exact on-chain hash (case-insensitive) — what a customer pastes into a ticket

referencestring

exact reference match

customer_guidstring

scope to a CYBRID customer guid, resolved to the account(s) holding it (other providers write their own id shapes into the same column and are not searched); a guid belonging to nobody returns an EMPTY page, never the tenant

overpaid'only' | 'exclude'

only | exclude — rows whose summed ROUTED settlements EXCEED notional_uoa. A memo is a payer-supplied bytes32 that can be routed more than once, and a route may declare a larger notional than the request asked for; either way the receiver holds more than the record says was owed.

limitinteger

page size

offsetinteger

page offset

Response

OK

limitinteger
offsetinteger
tenant_idstring
totalinteger

Changes

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