Skip to main content
POST
Create file previews in batch
Create presigned preview URLs for several S3 paths in a single request, instead of calling POST /files/preview once per file.

Request Parameters

Request Body

Response

previews contains one entry per requested path, in request order, each echoing its s3Path so you can map URLs back to files without relying on order alone.
All-or-nothing. If any path in s3Paths is invalid, the whole request fails with a 422 and no partial results are returned. Check errors[] in the problem response for the failing field.
Presigned URLs are short-lived (about one hour). Request them when you are ready to use them rather than caching them.

Idempotency

Idempotency-Key is accepted for client uniformity but ignored here: the presigned URLs expire well inside the 24-hour replay window, so a replayed response would hand back URLs that are already dead. Every request executes fresh. See Idempotent requests.

Authorizations

x-api-key
string
header
required

API key for authentication

Headers

Idempotency-Key
string

Accepted for client uniformity but IGNORED on this endpoint. It has no side effects, and its presigned URLs expire in an hour — well inside the 24h replay window — so a replayed response would carry URLs that are already dead against S3. Every request executes fresh: no 24h window, no replay, no Idempotent-Replayed header, and no key-reuse 422.

Body

application/json
s3Paths
string[]
required

S3 paths to sign, at most 100 per request.

Required array length: 1 - 100 elements
Example:

Response

A signed URL is returned for every requested path

previews
object[]
required

One entry per requested path, in request order. All-or-nothing: an invalid path fails the whole request rather than returning partial results.