Autorender API

v1.0.0

The Autorender API uploads files to your workspace and manages the files, folders, and sources in it. Every request goes over HTTPS and carries your API key.

API Base URL

Live Server:https://upload.autorender.io

Authentication

Every request needs your API key. Send it in one of two headers:

Authorization: Bearer YOUR_API_KEY

x-api-key: YOUR_API_KEY

Requests over plain HTTP, or requests with no key, fail. Create and manage keys in the dashboard — see Create an API key.

Key types and scope

Your workspace has two kinds of key, and the API enforces the difference on every request. The public key may only upload. It is created with your workspace, visible in full in the dashboard, and safe to embed in browser or mobile code, because uploading is all it permits. A private key may do everything. It is shown once when you create it, and belongs on your server only.

Endpoint	Public key	Private key
`POST /uploads`	✅	✅
`POST /uploads/remote`	✅	✅
`POST /multipart/start`	✅	✅
`POST /multipart/complete`	✅	✅
`GET /files`	❌ `403`	✅
`GET /files/{fileNo}`	❌ `403`	✅
`PATCH /files/{fileNo}/rename`	❌ `403`	✅
`DELETE /files/{fileNo}`	❌ `403`	✅
`GET /folders`	❌ `403`	✅
`POST /folders`	❌ `403`	✅
`POST /folders/rename/{folderNo}`	❌ `403`	✅
`DELETE /folders/{folderNo}`	❌ `403`	✅
`GET /sources`	❌ `403`	✅
`POST /sources`	❌ `403`	✅
`GET /sources/{sourceId}`	❌ `403`	✅
`PATCH /sources/{sourceId}`	❌ `403`	✅
`DELETE /sources/{sourceId}`	❌ `403`	✅

Uploading a part is not in the table because it goes straight to storage on a presigned URL and carries no API key. A public key on any other endpoint returns 403 with a message naming the fix:

{
  "success": false,
  "error": "This endpoint requires a private API key.",
  "message": "Your public key can only be used to upload. Create a private key in Configurations → API Keys and use it from your server for this operation."
}

We store every key as a SHA-256 hash and never keep the plaintext of a private key, so copy it when you create it — you cannot retrieve it afterward. The public key is stored so the dashboard can keep showing it to you, since it is meant to be published.

Response codes

Every endpoint returns one of these status codes. Successful responses are wrapped as { "success": true, "data": { ... } } unless the endpoint notes otherwise.

Code	Meaning
`200`	Request succeeded
`400`	The request body or parameters were invalid
`401`	The API key was missing or invalid
`403`	The key is not allowed on this endpoint — a public key was used for something other than uploading
`404`	The requested file or folder does not exist
`500`	Autorender hit an unexpected error while processing the request

Rate limit

Rate limits apply per endpoint and scale with your plan. Requests that exceed a limit receive a 429 response — pause briefly and retry. Contact us if you need higher limits.

Additional Information

Next steps

Direct upload

Upload a file from your backend with multipart/form-data.

Create an API key

Generate and manage the keys that authenticate your requests.

Get started

Endpoints

Autorender API

Autorender API

Authentication

Key types and scope

Response codes

Rate limit

Next steps

Direct upload

Create an API key

​Autorender API

​Authentication

​Key types and scope

​Response codes

​Rate limit

​Next steps

Direct upload

Create an API key

Autorender API

Authentication

Key types and scope

Response codes

Rate limit

Next steps