Confirm uploaded files so they are retained in Upwork storage. Uses the same attachment backends as start_attachment_upload. Requires the upload context and the file_uid values returned from upload.
WRITE OPERATION — REQUIRES EXPLICIT USER CONFIRMATION.
You MUST present full action details and receive explicit approval before executing. Each write requires separate confirmation even if the user said "approve all".
Actions:
- confirm: context (string, required) selects the attachment backend: messages = room message attachments (requires room_id); proposals = job-application/proposal attachments; offer = offer attachments; milestones = milestone attachments; job = job posting attachments; invitation = attachments when a freelancer accepts a client invitation. If the user did not clearly say where the file belongs, ask which context they want before calling start_attachment_upload. Params: file_ids (array of strings, required — file_uid values to confirm); task_id (string, required — the task_id returned by start_attachment_upload for these files). Only file_uid values that get_upload_status reports as done for that task_id can be confirmed; anything else is refused. Upload sessions last 30 minutes, so confirm promptly. Files uploaded through the inline component are already stored and must NOT be confirmed. Use the same context as the upload session that produced the file_uid values.
ConnectorOAuth