---
title: "Send download emails for many orders"
description: "Send the download email again for several orders at once, in the background, as the Orders page's bulk Send emails does. ids are order ids, Shopify order gids or ids, or order names."
url: https://docs.filemonk.io/v2/api-reference/orders/send-download-emails-for-many-orders/
api: "API v2 reference"
method: POST
path: "/orders/send_emails"
---

# Send download emails for many orders

`POST https://app.filemonk.io/api/v2/external/orders/send_emails`

Send the download email again for several orders at once, in the background, as the Orders page's bulk Send emails does. ids are order ids, Shopify order gids or ids, or order names.

**Note:** Queued: the response lists the orders that will be emailed and the ids that matched nothing. Each send charges usage, fulfils in Shopify when that setting is on, and assigns owed licence keys.

## Request body

- `ids` (array of strings, required)

Rate limit: this call costs 2 points ([rate limits](https://docs.filemonk.io/v2/errors-and-rate-limits/)).

## Example request

```sh
curl -X POST "https://app.filemonk.io/api/v2/external/orders/send_emails" \
  -H "X-Auth-Token: $FILEMONK_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "ids": [
      "3e84eb8d-e1d9-4e92-a4b2-a419c7f1122f"
    ]
  }'
```

## 200

Success: the write completed; the body is the updated resource.

## 202

Accepted: the change was saved and the rest of the work (emails, Shopify sync, a bulk job) continues in the background. The body is the resource snapshot plus `queued: true`; there is nothing to poll.

```json
{
  "queued": true,
  "count": 1,
  "ids": [
    "3e84eb8d-e1d9-4e92-a4b2-a419c7f1122f"
  ],
  "missing": []
}
```

## 401

Missing or invalid API key.

```json
{
  "errors": [
    "Invalid API key"
  ]
}
```

## 404

The resource does not exist for this shop, or the action path is not registered.

```json
{
  "errors": [
    "Order not found: c3d4e5f6-7a8b-4c9d-8e0f-1a2b3c4d5e6f"
  ]
}
```

## 422

The request failed validation, or sent a key the action does not take (`code: "unknown_parameters"` with `unknown` and `accepted`). Nothing was saved.

```json
{
  "errors": [
    "access.download_limit_count must be an integer of at least 0"
  ],
  "field_errors": {
    "access.download_limit_count": [
      "must be an integer of at least 0"
    ]
  }
}
```

## 429

Rate limited. Cost-weighted per API key, shared with API v1: a read costs 1 point, a write 2, 40 points per fixed 60-second window. Every response carries `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` (Unix time the window ends); a 429 adds `Retry-After` (seconds), `retry_after`, `retryable: true` and a `next_step` in the body. A 429 did nothing: wait `retry_after` seconds, then send the same request again. The budget is per key, so every tool or script using the key shares it; prefer one list call with `per_page` over many single reads.

```json
{
  "errors": [
    "You have exceeded the rate limit of 40 points per 60 seconds. Read requests cost 1 point(s) and write requests cost 2 point(s). Please retry after 12 second(s)."
  ],
  "code": "rate_limited",
  "retry_after": 12,
  "error": "Rate limit exceeded",
  "message": "You have exceeded the rate limit of 40 points per 60 seconds. Read requests cost 1 point(s) and write requests cost 2 point(s). Please retry after 12 second(s)."
}
```