POST
Re-send an order confirmation

Authorizations

Authorization
string
header
required

A secret API key. Publishable keys cannot reach this API. A key may carry an expiry, and an expired key is refused exactly like an unknown one, with a 401 that names no reason; check the key's expires_at in the dashboard rather than inferring it from a response. When a merchant rolls a key's secret they choose a grace window of up to 3 days, and for its duration BOTH the new secret and the one it replaced authenticate, so an integration moves over on its own deploy schedule instead of at the instant the button is pressed. Move before the window closes: after it, the old secret is refused. Nothing else about this contract moves with a roll. The key keeps its id and its scopes, so the only thing an integration updates is the credential itself.

Headers

Idempotency-Key
string
required

A unique key per logical write. Replaying a request with the same key returns the first response byte for byte instead of applying the write twice.

Path Parameters

orderId
string
required

Body

application/json

Takes no parameters, and an empty body is expected. Sends the order's confirmation email again, for a customer who says theirs never arrived. THE RECIPIENT IS READ FROM THE ORDER and cannot be named. to, to_address, email, recipient, address, cc, bcc, from and customer_id are each REFUSED BY NAME rather than ignored: that parameter is the entire difference between a resend and an open relay pointed at this merchant's sending domain and reputation. The copy is refused too, for the reason POST /notifications/test records: subject, body, template and payload all come from the store's own template for the event. THIS IS THE MIRROR OF THE TEST SEND. That route lets you name an address and refuses the copy; this one lets you name neither, because the address already exists on the order and any other would be mail the merchant did not authorise. IT SENDS REGARDLESS OF ANY PRIOR ATTEMPT, which is what makes it a resend rather than a dispatch. The send log keeps one "sent" marker per order, so a second call mails the customer again and leaves that marker alone; the response still reports what happened. USE A FRESH Idempotency-Key ON EVERY DELIBERATE RESEND, and reuse the key when RETRYING one. A replayed key answers with the first call's outcome and sends nothing, which is exactly what stops an ordinary network retry from putting a duplicate in a shopper's inbox. 200, not 201: nothing addressable is created here. The response carries the notification id so you can follow the delivery on GET /api/v1/notifications/{notificationId}. A FAILED DELIVERY IS STILL A 200, carrying status "failed" and a null notification_id. The request was carried out and the provider declined, which is an outcome rather than a fault of yours; a 5xx would release the idempotency reservation and your retry would send the email again. The provider's own error text is not published: it is written by a third party and can quote the recipient address back, which this response withholds.

Response

Success

data
object