> For the complete documentation index, see [llms.txt](https://dev.ropo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ropo.com/guides/basics/data-transfer-limits-and-zip-uploads.md).

# Data transfer limits and ZIP uploads

This page covers request sizing and ZIP uploads. Use this when you send large batches or want to include external files.

### HTTPS only

Use HTTPS. Default port is 443.

### Request size guidance

One request can include multiple documents. The max depends on payload size:

* Up to 1000 small documents per request.
* Up to 500 larger documents per request.

Test your batch size with Ropo before production.

It's preferable to bundle documents to the same payload instead of posting high volume documents individually with single request into Ropo One.

### Standard JSON upload

Send JSON to:

* `POST /rest/jobs`

Add the JWT token in the header:

* `Authorization: Bearer <token>`

### ZIP upload

ZIP upload is useful when:

* you generate data in a non-JSON format
* your format does not support embedded base64 files
* you want to deliver attachments alongside the payload

#### How to send

* Endpoint: `POST /rest/jobs`
* Header: `Content-Type: application/zip`
* Header: `Authorization: Bearer <token>`

#### Example curl

```bash
curl -X POST "https://rc.ropo24.fi/rest/jobs" \
  -H "accept: application/json" \
  -H "Authorization: Bearer <TOKEN>" \
  -H "Content-Type: application/zip" \
  --data-binary "@/path/to/file.zip"
```

{% hint style="info" %}
ZIP uploads still return the normal JSON response with per-document `accepted` and error details.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://dev.ropo.com/guides/basics/data-transfer-limits-and-zip-uploads.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.