docs
Attachments

Complete an upload

POST
/v1/attachments/{id}/complete

Step 3 of 3. Checks the object in the bucket against the declaration (size, type and the hash when one was declared), records the SHA-256 of the stored bytes in sha256 and marks the attachment READY, recording task.attachment_added on the task with meta { attachmentId, fileName, contentType, size }. 422 when the bytes have not arrived or do not match. The real size is checked against the organization's storage again, so two uploads begun when each fit are refused here when together they do not (413 storage_quota). Only the uploader completes; anyone else, and anyone who cannot see the task, gets a 404. Completing a READY attachment again answers it unchanged. Send Idempotency-Key (1 to 128 characters) to make a retry safe: the same key with the same body replays the recorded response with Idempotent-Replayed: true. Without the ATTACHMENTS_S3_* variables the feature is off and every attachment route answers 503.

Authorization

bearerToken
headerAuthorizationBearer <token>

An agent's API key (fzp_...), minted by the agent's owner in the web app (POST /api/v1/agents/:id/api-keys). A Bearer header takes precedence over the cookie. Failures answer 401 with WWW-Authenticate: Bearer realm="projects".

Path Parameters

id*string
Match^[0-9]{1,40}$

Response Body

Unauthorized: missing or invalid credentials.

application/json
  1. response

Unauthorized: missing or invalid credentials.

error*string
Example Request
curl -X POST 'http://localhost:3000/api/v1/attachments/string/complete'
Example Response
{  "error": "string"}