Skip to main content
GET
Get a signed URL for a human step's input file
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.

v2 compatibility notes

Returns a short-lived signed URL for one file a human step was handed. The read is recorded first, under your credential and the request id (file read audit); a read that cannot be recorded is refused with 503 and no URL is minted. Who may open the step is the same as for listHumanTaskInputFiles. A file that is not one of the step’s inputs answers 404, as does a step the owner may not open, or stored content with no URL. A platform key or an External App gets 403 with error.personRequired: true.

Parameters

Example

The MCP tool forge_get_human_task_input_file_url returns the same data and meta.

Authorizations

Authorization
string
header
required

A Personal key (fmcp_…), bound to the person who created it, or an interactive MCP sign-in that resolves to one. Pass as Authorization: Bearer <key>. It acts for that person, under their role grants narrowed by its scopes; an operation that acts for a person admits only this kind.

Path Parameters

fileId
string
required

The input file's fileId from listHumanTaskInputFiles.

Minimum string length: 1

Query Parameters

id
string

The human step's node run id.

Minimum string length: 1
humanTaskId
string

The step's human task (getHumanTask's humanTaskId), for a caller with no node run id, such as one who reached the task through getHumanTask or attention rather than My Work.

Minimum string length: 1

Response

The signed URL

data
object
required
meta
object
required