Trigger Fileflare to send (or re-send) the download email for an order. Uses the order’s existing customer email and the current asset state. The same call doubles as a “force re-send” for orders where the customer says they didn’t get the email.
Requires Bearer authentication. Rate-limited to 30 requests per minute (stricter than the standard 60/min) to prevent accidental email blasts.
Endpoint
PUT https://app.digital-downloads.com/api/v1/orders/{order}
Parameters
Path
{order}— the Fileflare order ID (a UUID): theidreturned by Viewing orders. It is not the Shopify order ID or the order number.
Example request
curl -X PUT https://app.digital-downloads.com/api/v1/orders/9b1c6a52-3f0e-4c7a-8d21-5e7f4a0c1b33 \
-H "Authorization: Bearer YOUR_API_KEY"
Example response — 201 Created
The response body is empty. The 201 status means the request was accepted, not that an email went out: Fileflare rebuilds the order’s download links first and sends the email only if the order has at least one link. An order with no attached files returns 201 and sends nothing.
Notes
- The email goes to the order’s current customer email. If you’ve updated the email on the Shopify order, the next send uses the updated address.
- Subject and body come from your email template.
- A send also sets the order’s
email_sent_at(see Viewing orders). - Bulk: the bulk send tool emails past buyers about asset updates and release dates, not individual orders. To send many orders, script this endpoint and stay under 30 requests per minute.
Common errors
- 404 — no order matches that ID.
- 401 — missing or invalid API key.
- 429 — exceeded 30 sends per minute. Slow down.