Skip to content

API reference

Cancel upload

documents.CancelUploadWriteAPI key

Cancel an unfinished upload owned by this credential. Completed files must be removed through the document API.

POST/v1/operations/documents.CancelUpload
On this page

Access & visibility

Allow documents.CancelUpload on your API key.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

upload_idstringRequired

Keep the upload_id and the same credential and acting member throughout the upload. Completion returns a separate file_id. documents.CreateUpload.

At least 1 character.

Where this fits in an upload

The file guide includes a streaming Node.js helper and the complete HTTP sequence: create an upload, request a signed URL for each part, PUT the bytes directly to that URL, then complete the upload. Never send the Brigg API key to a transfer URL.

Keep the same credential and acting member for every step. Follow the returned part size and count rather than imposing your own split. Completing with only upload_id lets Brigg collect part receipts. A successful byte transfer is not a completed file: verification and scanning must finish before you receive a usable file_id.

Retain upload_id for recovery. Read its state before retransferring an interrupted upload; ready returns the existing file ID, while an expired upload requires a new start. Temporary transfer URLs and completed file IDs have different lifetimes.

Response

Returns 200 OK with a JSON body.

cancelledbooleanRequired

Whether the unfinished upload was cancelled.

Errors & retries

Set BRIGG_REQUEST_ID once for each logical action. The samples send it as Idempotency-Key. Reuse the same value and body on retries, including after a timeout; a missing response does not prove the action failed.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types. Supply a stable Idempotency-Key containing 1–200 characters.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying. Reuse the original Idempotency-Key.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "upload_id": {
      "type": "string",
      "minLength": 1,
      "description": "Keep the upload_id and the same credential and acting member throughout the upload. Completion returns a separate file_id. [documents.CreateUpload](/reference/documents/CreateUpload)."
    }
  },
  "required": [
    "upload_id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "upload_id": "upl_example"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "cancelled": {
      "type": "boolean",
      "description": "Whether the unfinished upload was cancelled."
    }
  },
  "required": [
    "cancelled"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "cancelled": true
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.