This is a procedure-sandbox session endpoint, not a Forge Platform API v3 operation. The Procedure SDK calls this
/api/v1/proceduresApi/* protocol with the invocation’s session token.POST /api/v1/proceduresApi/putFile
Sandbox-side counterpart to the agent putFile tool. A procedure POSTs to this endpoint to persist file bytes through the platform’s file_hosting capability and create a fileBindings row in the appropriate domain. The body uses the same input schema as the agent tool.
Authentication
Bearer session token, minted for one procedure invocation. A token whose scope does not include file hosting returns403 CAPABILITY_DENIED.
Request body
The same discriminatedsource × bind shape as the agent tool — see Files and Bindings · putFile for the full schema.
Display filename. Surfaces in the Console attachments UI and in downstream tool calls. When omitted, the name comes from the binding and the mime type, not the source path: the
outputKey for workflow_output, otherwise scratch, file or attachment, plus the mime type’s extension. Supply filename to keep the source name.Mime type for downstream extractors (for example
application/pdf or text/csv). Inferred when omitted.Responses
400 — INVALID_INPUT
400 — INVALID_INPUT
Body fails validation. Check the
source and bind shapes above.401 — AUTH_FAILED
401 — AUTH_FAILED
Missing or invalid bearer session token.
403 — CAPABILITY_DENIED
403 — CAPABILITY_DENIED
The session token’s scope does not include file hosting. The body’s
decisionId names the Trust Fabric decision that recorded the refusal.404 — NOT_FOUND
404 — NOT_FOUND
The procedure version the session token names has no stored manifest.
413 — PAYLOAD_TOO_LARGE
413 — PAYLOAD_TOO_LARGE
The request exceeds the platform’s argument limit. Write the file in the VM and use a
sandbox or uploadUrl source.500 — INTERNAL_ERROR
500 — INTERNAL_ERROR
Upload or persistence failure. Details in the response
message.Related
- Files and Bindings — the agent-side surface; the same
sourceandbindschema - Procedures domain index

