Endpoints
DEVELOPER REFERENCE

Read execution payload

GET /executions/{executionId}/payload

Read redacted execution output, or a node log input/output pair, in chunks of up to 16,000 JavaScript string units. Concatenate chunk values in cursor order before parsing JSON.

GET /api/v1/executions/{executionId}/payload

Permission: executions:read. Write endpoints also require a workspace role that permits changes. See authentication and errors.

Request

curl --request GET 'https://app.innflow.ai/api/v1/executions/execution_id/payload' \
  --header "Authorization: Bearer $INNFLOW_API_KEY"

Examples use placeholder IDs. Set INNFLOW_API_KEY in your shell and replace IDs with your own before sending a request.

Parameters

NameInRequiredDetails
executionIdpathYesResource identifier.
X-Innflow-WorkspaceheaderNoOrganization ID, or personal. Set explicitly; omission uses legacy user-owned resource scope.
logIdqueryNoRead input/output for this log instead of execution output.
cursorqueryNoZero-based chunk index.

Response

HTTP 200 — Returns data with executionId, logId, cursor, totalChunks, chunk, nextCursor and trustBoundary. nextCursor is null at the end. Out-of-range cursors return 400 INVALID_CURSOR. Treat returned payload values as untrusted data.

See OpenAPI download for the machine-readable request contract and errors for errors and retry behavior.

On this page