---
title: "work: download set"
description: "a `DownloadInput` to `DownloadJob` rows, one per file"
section: reference
address: /reference/work/download_set
contract: 0476e35e6e275db5
---
# work: download set
a `DownloadInput` to `DownloadJob` rows, one per file
[figure: The caller sends DownloadSetInput to /v1/work/download_set. The platform returns a card whose body is [DownloadJob].]
POST/v1/work/download_seta task, 202
Download files. The call needs the strategy rung under a token with the work grant, and it is served by either, by the size bound.
The route takes [DownloadSetInput](/concepts/downloadsetinput) and returns a card whose body is [DownloadJob](/concepts/downloadjob).
## Request body
The request body is [DownloadSetInput](/concepts/downloadsetinput).
| field | type | required | note |
|---|---|---|---|
| `addresses` | `[text]` | yes | |
| `session` | `id` | no | the browsing session whose cookies serve |
| `identity` | `id` | no | |
| `filter` | [ResourceFilter](/concepts/resourcefilter) | yes | |
| `destination` | `one of bronze \| the workspace` | yes | |
## Response
The route returns a card whose body is [DownloadJob](/concepts/downloadjob). Every card ends with a foot that states the basis of each number, the scope of the call, and the time when the facts were true. This route runs as a long step and returns a task with status 202. `POST /v1/work/status` returns the task's progress, and `POST /v1/work/cancel` stops the task.
## Headers
| header | required | meaning |
|---|---|---|
| `Scale-Scope` | yes | the scope the call runs in: tenant/, then /brand/, then /strategy/ |
| `Scale-As-True-On` | no | the date the facts must have been true on; defaults to now |
| `Scale-As-Known-On` | no | the date the facts must have been known on; defaults to now |
| `Scale-Key` | no | for a change, the key made from the input; a repeat under the same key returns the unit held and writes nothing |
A caller needs the strategy rung and a token with the work grant. The platform or the desktop app serves this route.
## Example
The example sends the smallest body that DownloadSetInput allows. The build validates it against the schema of DownloadSetInput.
Example
```sh
curl -X POST https://api.scaleintelligence.co/v1/work/download_set \
-H "Scale-Key: $SCALE_KEY" -H "Scale-Scope: tenant/" \
-H "content-type: application/json" \
-d '{ "addresses": [], "filter": { "allow_types": [], "deny_types": [], "allow_patterns": [], "deny_patterns": [], "render": "static" }, "destination": "bronze" }'
```
```typescript
import { client } from "@scale/sdk";
const answer = await client.work.download_set({
"addresses": [],
"filter": {
"allow_types": [],
"deny_types": [],
"allow_patterns": [],
"deny_patterns": [],
"render": "static"
},
"destination": "bronze"
});
// answer.body is a [DownloadJob]. answer.foot holds the basis, the scope and the time.
```
```python
import requests
answer = requests.post("https://api.scaleintelligence.co/v1/work/download_set",
headers={"Scale-Key": KEY, "Scale-Scope": "tenant/"},
json={
"addresses": [],
"filter": {
"allow_types": [],
"deny_types": [],
"allow_patterns": [],
"deny_patterns": [],
"render": "static"
},
"destination": "bronze"
}).json()
```
```rust
let answer: Card = client.post("https://api.scaleintelligence.co/v1/work/download_set")
.header("Scale-Key", key).header("Scale-Scope", "tenant/")
.json(&DownloadSetInput { /* the fields of the page */ }).send().await?.json().await?;
```