Fulfillments
Mark orders fulfilled and read fulfillment state.
Mark an order fulfilled once the goods have been handed over — built for digital-delivery integrations, so the merchant’s Orders view stops showing every digital sale as perpetually unfulfilled. Fulfillment through the API is all-or-nothing: a fulfillment covers every line item on the transaction (partial, per-item fulfillment stays a dashboard workflow), and no customer notification is sent. Works with a merchant key or an app access token; scoped keys need fulfillments:read / fulfillments:write.
List fulfillments
List the fulfillments on one transaction. fulfillment_status is the order's own roll-up ('unfulfilled' or 'fulfilled'), so you never have to derive it. Requires the fulfillments:read scope on scoped keys.
https://paysio.com/api/v1/fulfillmentsAuthorizations
Any API key. Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.
Query parameters
Required. The transaction to inspect
Mark an order fulfilled
Create a fulfillment covering every line item on the transaction and flip the order's fulfillment status. Returns 400 with code 'already_fulfilled' when the order is already fully fulfilled. Requires the fulfillments:write scope on scoped keys.
https://paysio.com/api/v1/fulfillmentsAuthorizations
Secret key (sk_*) or app access token. Prepend your key with Bearer, e.g. Bearer sk_test_your_secret_key.
Body
The transaction to fulfill
Optional tracking number (max 200 chars)
Optional carrier name (max 60 chars)
Optional tracking URL
Optional note (max 1000 chars)