Version 1.4.0 - Orders & Transactions API

Released on July 29, 2026

This release exposes the order and payment lifecycle through the REST API, so integrations can create orders, charge them, and complete them programmatically.

Highlights

Orders REST API

Manage the full order lifecycle under /v1/orders:

• POST /v1/orders creates an order in pending status (no payment).
• GET /v1/orders and GET /v1/orders/{order_number} list and retrieve orders.
• PATCH /v1/orders/{order_number} edits an order while it has not settled.
• POST /v1/orders/{order_number}/complete completes the order and fires the normal completion logic, including any applicable auto responders. The call is idempotent.

Transactions REST API

POST /v1/transactions attempts the payment for an existing order immediately. Transactions are not drafts — hitting the endpoint is equivalent to attempting the charge. The campaign’s configured gateway is used by default, and a valid gateway_id override is accepted. The order’s payment status is reflected (processing / declined), while completion and auto responders remain an explicit, separate step.

See Orders & Transactions API for request and response examples.

Breaking Changes

None - this release is fully backward compatible.

Note: A new api:transactions.create token permission gates the transaction charge endpoint.