--- title: "Download a finished trader export" method: GET path: "/api/v1/trader/{address}/export/download" tags: ["Traders"] --- # Download a finished trader export `GET /api/v1/trader/{address}/export/download` Redirects (302) to a short-lived presigned URL for the finished export file while the job status is 'ready' and expires_at has not passed. The file is gzip-compressed and served with the format's Content-Type (application/json, application/x-ndjson, or text/csv). Returns 400 while the job is queued, running, cancel_requested or reconciling (poll the status route first) and for a failed or cancelled job (submit a new export); returns 410 with error.code not_found and error.reason export_expired once the retention window has passed or the file has been retired, so the redirect never points at a file that is gone. ## Path parameters - `address` string, required ## Query parameters - `job_id` integer, required ## Headers - `X-Query-Validation` 'strict' ## Other responses - `302` — Redirect to the presigned download URL. - `400` — Invalid request parameter - `401` — Missing or invalid API key - `402` — Active Pro subscription required. The key is valid but the account has no active Pro subscription; error.reason is subscription_inactive and error.message names the reactivation URL (https://0xinsider.com/billing). Permanent until a person reactivates: no Retry-After, never retry on a schedule. - `403` — Account access denied - `404` — Resource not found - `408` — The handler did not answer inside the server's 30-second timeout. error.code is request_timeout. On GET and HEAD the response carries Retry-After and error.retry_at; on a mutation it carries neither, because the request may have completed on the server: check its state before repeating it, and reuse its Idempotency-Key. - `410` — The export's retention window has passed and its file is retired. error.code is not_found, error.reason is export_expired, error.message names expired_at. Submit a new export; polling or retrying the download cannot succeed. - `423` — Account is locked - `429` — Rate limit exceeded. Three independent budgets. (1) 100 requests/minute per user (sliding window), on every authenticated route. (2) On the BATCH routes only: 2500 batch item units/minute per user, reserved before any item is executed. A batch with N requested items costs N item units, including duplicate and invalid items. 2500 = 100 requests x 25 items per batch, which is the most item work a key can buy through the request limiter at all: a caller may spend their entire 100-request minute on full 25-item batches without the item budget being what stops them. The REQUEST budget is the effective ceiling, and batching is never the more expensive choice. The item budget can still deny at a sliding-window boundary (both counters carry the previous window forward with a floor, and the item counter runs 25x the request counter), so honor a 429 from either. Over-quota batches return 429 with Retry-After plus RateLimit-Limit, RateLimit-Remaining, and RateLimit-Reset before any item work is done. (3) The monthly quota: Pro includes 250,000 authenticated requests per UTC calendar month, whatever the billing cadence. Over 250,000: with pay as you go on, requests keep answering and the excess bills at USD 0.20 per 1,000 on a monthly invoice, up to 1,000,000 requests a month; without it, from October 1, 2026, the next request answers 429 rate_limited with error.reason monthly_quota_exceeded and a Retry-After to the month's reset, and from the same day a pay-as-you-go account answers the same past 1,000,000. A refused request is not counted. Every authenticated response carries X-Monthly-Quota-Limit, X-Monthly-Quota-Remaining, and X-Monthly-Quota-Reset (unix seconds, the first of next month). (4) The per-address budget: 1200 requests/minute per IP, shared by every caller behind one address and counted before authentication, on every route. A 429 from it carries error.reason ip_rate_limited and describes that bucket in RateLimit-*; a throttled address (sustained over-limit traffic) carries error.reason ip_throttled with a Retry-After of minutes to days, and a request before it does not shorten the cooldown. Every 429 is the standard error envelope with meta.request_id equal to X-Request-Id. - `500` — Unexpected server error - `503` — Redis-backed authenticated rate limiter unavailable; retry after the per-process outage cooldown ## Changes - **2026-09-23** `ece7a25b7a44` — 11 warning, 11 info - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `400` - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `401` - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `402` - added the new `freshness_ceiling_unsatisfied` enum value to the `error/reason` response property for the response status `403` - …18 more - **2026-09-23** `8462acf80f8c` — 10 warning, 1 info - added the new `export_expired` enum value to the `error/reason` response property for the response status `400` - added the new `export_expired` enum value to the `error/reason` response property for the response status `401` - added the new `export_expired` enum value to the `error/reason` response property for the response status `402` - added the new `export_expired` enum value to the `error/reason` response property for the response status `403` - …7 more - …earlier changes not shown [Full history](https://skmtc.dev/0xinsider/apis/0xinsider-api/changes/api/v1/trader/:address/export/download/get.md) --- [API](https://skmtc.dev/0xinsider/apis/0xinsider-api.md) · [All operations](https://skmtc.dev/0xinsider/apis/0xinsider-api/llms.txt) · [OpenAPI document](https://skmtc.dev/0xinsider/apis/0xinsider-api/revisions/2035b3316329?raw)