Confirm Upload

curl -X POST https://api.onepin.ai/api/v1/uploads/upload_id \
     -H "Authorization: Bearer <token>" \
     -H "Content-Type: application/json" \
     -d '{
  "context_type": "workflow",
  "context_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
}'

{
  "data": {
    "id": "d290f1ee-6c54-4b01-90e6-d701748f0851",
    "user_id": "7c9e6679-7425-40de-944b-e07fc1f90ae7",
    "filename": "project_script.txt",
    "category": "script",
    "content_type": "text/plain",
    "status": "uploaded",
    "created_at": "2024-01-15T09:30:00Z",
    "updated_at": "2024-01-15T09:30:00Z",
    "workspace_id": "1a2b3c4d-5e6f-7a8b-9c0d-1e2f3a4b5c6d",
    "format": "txt",
    "size_bytes": 20480,
    "char_count": 15000,
    "line_count": 500,
    "download_url": "https://api.onepin.ai/downloads/d290f1ee-6c54-4b01-90e6-d701748f0851?expires=1687000000",
    "context_type": "workflow",
    "context_id": "3fa85f64-5717-4562-b3fc-2c963f66afa6"
  },
  "meta": {
    "request_id": "req_1234567890abcdef",
    "timestamp": "2024-01-15T09:30:00Z"
  }
}

Confirm a completed upload and bind it to a resource (step 2 of 2).

Call this after successfully PUTting your file to the presigned URL returned by POST /uploads. Provide context_type and context_id to associate the file with an existing resource (currently workflow is the supported context type). The file is moved to its final location and status transitions from pending to uploaded.

This endpoint is idempotent: if the upload was already confirmed, the current state is returned without re-processing.

Storage quota is checked against the workspace at confirm time. If confirming would exceed the workspace storage limit, a 402 is returned and the file remains in its staging location (the upload record stays pending so you can delete the staging file and try a smaller file).

Binding to a workspace-scoped resource requires the caller to be a member of that workspace. Workspace is inferred from the resource when X-Workspace-Id is omitted.

Dual-auth: Bearer JWT or API key (scope uploads:write).

Confirm a completed upload and bind it to a resource (step 2 of 2). Call this after successfully PUTting your file to the presigned URL returned by `POST /uploads`. Provide `context_type` and `context_id` to associate the file with an existing resource (currently `workflow` is the supported context type). The file is moved to its final location and `status` transitions from `pending` to `uploaded`. This endpoint is idempotent: if the upload was already confirmed, the current state is returned without re-processing. Storage quota is checked against the workspace at confirm time. If confirming would exceed the workspace storage limit, a 402 is returned and the file remains in its staging location (the upload record stays `pending` so you can delete the staging file and try a smaller file). Binding to a workspace-scoped resource requires the caller to be a member of that workspace. Workspace is inferred from the resource when `X-Workspace-Id` is omitted. Dual-auth: Bearer JWT or API key (scope `uploads:write`).

Authentication

AuthorizationBearer

Clerk JWT token

AuthorizationBearer

Onepin live API key (op_live_...). Test and public keys are reserved in Phase 1.

Path parameters

upload_idstringRequiredformat: "uuid"

Request

This endpoint expects an object.

context_type"workflow"Required

Type of resource this upload is being attached to. Currently only workflow is supported.

context_idstringRequiredformat: "uuid"

ID of the resource to attach this upload to. Must be an existing resource of the given context_type that the caller has access to.

Response

Successful Response

dataobject

metaobject

Errors

422

Unprocessable Entity Error