Overview

The /v2/invoices API creates purchases and provides checkout, payment, and delivery actions. It keeps the existing order-level response format. For new integrations that read purchase state, use Orders; for one sale record per purchased variant, use Order line items.

Create an invoice with current-store variant IDs, then create a checkout session when the response does not already contain a checkout URL. Never infer payment success from a browser redirect. Use signed webhooks or retrieve current state.

Manual completion can trigger delivery and should be used only after payment is independently confirmed. Fulfillment retry operations reset existing retryable delivery tasks rather than creating another purchase. Treat deliverables as sensitive.

The OpenAPI-rendered operations are the source of truth for invoice fields and response shapes.

Endpoints

• List all invoices
• Search invoices
• Create an invoice
• Retrieve an invoice
• Create a checkout session
• View invoice deliverables
• Mark pending invoice completed
• Mark pending invoice voided
• Update invoice status
• Refund an invoice
• Retry invoice fulfillment
• Retry dynamic delivery
• Resend invoice deliverables
• Issue replacement

See Create a checkout and Fulfil an order.