API frequently asked questions
Find the correct integration guide and avoid duplicate live orders.
Which plan includes API access?
Base and Pro both include API access. A valid Roastify fulfillment payment method is required for live orders. Compare plans.
Can I test without producing real coffee?
Use a test API key and the order simulator. Keep test and live keys separate. Requests made with a live key can create real charges and fulfillment. Set up your integration.
Can the API create a Merchant App product?
The headless flow is Create Artwork, then Create Order. There is no Create Product endpoint for adding a saved product to the Merchant App catalog. See artwork generation and the order reference.
An order request timed out. Should I submit it again?
First check whether the order exists. Use a unique idempotency key for each intended operation and reuse it for a retry of that same operation. Follow the idempotency guide; do not create a fresh key to retry an uncertain order.
Which artwork template should I use?
Use the template for the actual product and package. An artwork URL must be reachable over HTTPS and return a supported image. A valid response does not establish print quality or label compliance. Read the artwork requirements.
How do I follow fulfillment changes?
Use webhooks and verify signatures before trusting incoming events. For current endpoint fields, use the API reference rather than an old payload example.
Can I cancel an order or promise its delivery date?
Cancellation is a request, and production plus carrier transit are estimates. Read production times, including the larger-order exception.
Can I connect WooCommerce?
The old plugin is retired. A custom API integration is a development project; Roastify Stores is the hosted alternative. Compare selling options.
For an API issue, send support@roastify.app the endpoint, status code, time, test or live mode, and relevant request or order reference. Redact API keys and customer payment details.