Skip to main content
GET
Get a Trust Fabric attention item
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

Reads one attention item, decided ones included, by the resource it is about: a workflow run, a chat session, an approval, a human step or an agent setup request. Who reads as whom, and what ability means, are the same as for listAttention. An item you may not see, a missing resource and an id that does not name a resource of its kind all answer the same 404. An unknown kind is 400.

Parameters

Example

The response is { "data": { "item": { … } }, "meta": { "requestId": "…" } }; item follows the TrustAttentionItem schema. The MCP tool forge_get_attention_item returns the same data and meta.

Authorizations

Authorization
string
header
required

An External App: the JWT it obtains from POST /oauth/token with OAuth2 client_credentials. Pass as Authorization: Bearer <jwt>. An app's static companion key also authenticates as the app, but is deprecated and is not protected by Idempotency-Key.

Path Parameters

subjectId
string
required

The resource id: a run, chat session, approval, human step (node run) or agent setup request id.

Minimum string length: 1

Query Parameters

kind
enum<string>
required

The kind of resource the item is about.

Available options:
workflow_run,
chat_session,
approval,
human_node,
agent_setup

Response

The item

data
object
required
meta
object
required