Send an invoice

Finalizes a draft to open: mints a hosted checkout session and emails the customer. The optional body's notify: false finalizes without the checkout session or email, for callers that collect payment themselves. A notify send needs at least one payment_methods entry on the invoice and is rejected with 422 without one. It fails with 502 (invoice stays draft) if the checkout session cannot be minted.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Path Params
string
required

Invoice ID

Body Params

Send options

boolean

AllowDuplicate proceeds past the near-duplicate window after the caller
was shown the collision.

boolean
string

Origin identifies the source that triggered the send so the settled
payment is attributed to the right payment channel. Defaults to
"invoices" when omitted; a caller such as orders-api or subscriptions
passes its own source (e.g. "orders"). Must be a value checkout-api-go
and core-api allow.

Headers
string

Optional replay protection: repeating a send with the same key returns the already-sent invoice without minting a second checkout session or emailing the customer twice. Reusing a key with a different payload is rejected with 422; a concurrent in-flight duplicate answers 409. Max 255 characters, valid for 24h.

string

Email of the dashboard user triggering the send (the maker). Consumed by the maker-checker approval gate so a different user must approve; without it the requester falls back to the organization itself.

string

Id of the dashboard user triggering the send; pairs with X-Acting-User.

Responses

Language
Credentials
Basic
base64
:
URL
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json