Skip to main content
One order buys 1-10 packs of one kind for one wallet, paid with one payment. Create it with POST /orders, follow it with GET /orders/{id} or the nft_order.updated webhook, and prove the pull with GET /orders/{id}/verification.

Order statuses

The pull and the token

Once paid and opened, the order carries:
  • pull: the item pulled (card_id, category, name, value, pulled_at). pull.value is the item’s value when it was pulled; it anchors the sell-back offer.
  • token: the NFT. On EVM it has chain, contract, token_id, status and tx; on a Solana program it has collection and asset instead of contract.
token.status: pending (reserved, not sent), submitted, confirmed, failed (being retried), or burned once the token has been sold back or shipped.

Multi-pack orders

A multi-pack order (quantity 2-10) is one payment for quantity × the pack price. Each pack inside it is a unit: once the payment settles, every unit opens, mints and (if it has to) refunds on its own, exactly like a single order.
  • price is the total due; unit_price the price of one pack. Each unit is in the single-order shape plus batch_id and unit (1 to quantity), and carries its own pull and token.
  • GET /orders/{id} with your Idempotency-Key or the order’s id returns the whole order; with one unit’s id it returns that unit.
  • The order’s status: awaiting_payment until paid; once paid, the units’ status when they all agree (paid, rolled, minted, refund_due, refunded, expired, …); otherwise processing while any unit is still moving, and completed once every unit is final (for example some minted and one refunded).
  • Refunds are per unit. A unit that can’t open after payment goes to refund_due on its own and refunds its share of the payment. A payment that arrives after the 24-hour window refunds every unit its share (paid_after_expiry).
  • In GET /orders and in webhooks the units appear one by one, each with the order’s order_id, its batch_id and its unit number.

Provably fair

Every pack is opened provably fairly. GET /orders/{id}/verification returns the proof for an order’s pull, and a public verify_url your customer can open to re-run the check without a key.