Send an invoice
Emails the invoice to the address on it, with its PDF. Only while it can still be paid, and one invoice email a store in five minutes.
A payment link has no address on it until it is sent or paid, so the first send names one in email. The link is that buyer’s from then on: the page it is paid on stops asking who is paying, and a later send with no email goes to the same address. It cannot be sent to another address once somebody has started paying it (link_in_use).
A link that can be paid more than once stays nobody’s: every send names an email, which is only where that one email goes, and it may be sent to as many people as you like at the same pace.
Needs the invoices.write permission (Raise Invoices). It sends an email, and is counted against a budget of its own: 60 in ten minutes for each key.
Authorizations
A secret API key, made under Developers in the dashboard: Authorization: Bearer shoply_sk_...
Headers
A word of your own for this one change, up to 180 letters, digits, dots, dashes, underscores and colons. Sent again with the same key, the request is not carried out twice: the first answer comes back, with Idempotent-Replay: true.
Path Parameters
The store's ID. A key reaches the store it was made in: GET /key answers which.
The invoice's order.
Body
For a payment link: the address to send it to. Left out, it goes to the address already on it.
"buyer@example.com"
Response
It worked.
Whether the request did what was asked.
Words for a person. Empty when it worked.
Why it was refused, as a word that does not change. Empty when it worked.
The thing asked for: an object, or for a list its rows.
For a paged list: how many pages there are.
For a paged list: how many rows there are in all.
Anything else the route answers beside the thing itself.

