Skip to main content
PUT
/
v1
/
uploads
/
{uploadId}
Upload a file chunk
curl --request PUT \
  --url https://files.adclear.ai/v1/uploads/{uploadId} \
  --header 'Authorization: Bearer <token>'
{
  "uploadId": "3c90c3cc-0d44-4b50-8888-8dd25736052a",
  "bytesReceived": 123,
  "correlationId": "3c90c3cc-0d44-4b50-8888-8dd25736052a"
}

Documentation Index

Fetch the complete documentation index at: https://docs.adclear.ai/llms.txt

Use this file to discover all available pages before exploring further.

Authorizations

​
Authorization
string
header
required

Clerk session JWT or Unkey API key passed as Bearer token

Headers

​
x-adclear-workspace-id
string<uuid>

Workspace ID fallback. Required when authenticating with a Bearer token in environments where cookies cannot be shared (e.g. preview). Not needed for API key auth (workspace is embedded in the key metadata) or when the workspace cookie is present.

Example:

"43dc2a1c-3384-41b5-a6e9-3b2d607d0fae"

​
x-external-user-id
string

Required when authenticating with an API key. Identifies the end-user making the request. Ignored when authenticating with a Bearer token (the user ID is extracted from the token).

Example:

"user_abc123"

​
x-external-user-email
string<email>

Optional. Email of the external user, used for audit logging. Only applicable when authenticating with an API key.

Example:

"user@example.com"

Path Parameters

​
uploadId
string<uuid>
required

Upload ID

Response

Chunk accepted or upload completed

​
uploadId
string<uuid>
required
​
status
enum<string>
required
Available options:
uploading,
completed
​
bytesReceived
integer
required

Total bytes the server has received so far

​
correlationId
string<uuid>
required

Correlation ID for request tracing. Include in support requests.