# Create a presigned staged upload batch

> Create staged upload records and return presigned S3 POST credentials.

POST

/sites/upload-batches/presign/

Get a presigned staged upload. This is step 1 of create, update (bundle replace), and file-operations put flows.

1.  Call this endpoint with `file_intents` (`client_ref` can be any unique id; `file_name` is the asset basename).
2.  Upload bytes to S3 with a multipart POST to `files[].upload_url` (no Rippling auth). Include every key in `files[].upload_fields`, then a final `file` part with the binary.
3.  Pass `files[].file_id` to create, update, or file-operations — not `upload_batch_id`.

### Required Scopes

-   sites.read-write
    

### Request

-   application/json

**Body**

**file\_intents** object\[\] required

Non-empty array of file upload intents to stage with presigned S3 upload URLs.

Array \[

**client\_ref** string required

Any unique client-chosen id echoed with the staged file\_id for correlation. Not used server-side beyond the response.

**file\_name** string required

File name with extension (e.g. site.zip). Used to derive Content-Type and create/PATCH asset type.

\]

## Responses

-   200

Successful response

-   application/json

-   Schema
-   Example (from schema)

**Schema**

**upload\_batch\_id** string

Identifier for the staged upload batch.

**files** object\[\]

Staged files created by the upload batch.

Array \[

**client\_ref** string

Any unique client-chosen id echoed with the staged file\_id for correlation. Not used server-side beyond the response.

**file\_id** string

Staged upload identifier for use in create, update, or file operations after uploading bytes to S3. The id can be reused for 1 hour from presign, each attach copies the bytes into that site's bundle, a repeat attach before expiry creates another bundle, and the staged object is removed after expiry.

**file\_name** string

Staged file name from the presign file\_name intent.

**status** string

Upload status. Returns awaiting\_upload after presign until the file is uploaded to S3. After the object exists in S3, status becomes active on first use. Attach does not consume the staged upload; it is removed after expiry.

**upload\_url** string

Presigned S3 POST URL for uploading the file bytes.

**upload\_fields** object

Form fields required for the S3 POST (send these before the file part).

\]

```json
{
  "upload_batch_id": "string",
  "files": [
    {
      "client_ref": "string",
      "file_id": "string",
      "file_name": "string",
      "status": "string",
      "upload_url": "string",
      "upload_fields": {}
    }
  ]
}
```

Source: https://developer.rippling.com/documentation/rest-api/reference/upload-batches-presign-sites

> For the complete documentation index, see [llms.txt](https://developer.rippling.com/llms.txt). Public pages have a Markdown version at the same URL with .md added.
