Upload File
Upload a file without triggering processing
on_conflict field:error(default) — if the uploaded filename matches a file already in the workflow, the whole request fails with409and lists the conflicting names (and the name each would take). Nothing is uploaded. This makes a rename an explicit opt-in, never a silent surprise.rename— the colliding file is auto-renamed by inserting a(n)counter before the extension (e.g.invoice.pdf→invoice (1).pdf). Each returned file’sfilenameis then the name it was stored under, andoriginal_filenameholds the name you uploaded (and isnullwhen no rename happened).
Request Body
This endpoint usesmultipart/form-data:
Authorizations
API key issued from app.anyformat.ai/api-key. Send as Authorization: Bearer <key>.
Path Parameters
Body
How to handle an uploaded filename that already exists in the workflow (filenames are unique within a workflow). error (the default) rejects the whole request with 409 and lists the conflicting names, so a rename is never silent — the caller must opt in. rename accepts the collision and lets the server auto-rename the file by inserting a (n) counter before the extension (invoice.pdf → invoice (1).pdf).
error, rename Response
Successful Response
Response from creating a file collection. Contains the collection ID and the status of each uploaded file.
Unique identifier of the newly created file collection.
"069dcc2c-e14c-7606-8000-2ee4fb17b4e1"
List of files included in the collection, with their upload status.
The UUID of the workflow this collection belongs to.
"0686bb97-8c30-70f0-8000-97669e000eb8"
Human-readable name for the collection.
Files the backend refused to accept — unsupported extension at slot-time or disguised bytes at register-time. Empty when every file uploaded cleanly.

