> ## Documentation Index > Fetch the complete documentation index at: https://yukta.infenia.com/llms.txt > Use this file to discover all available pages before exploring further. # Read part of the output of a node > Returns numbered lines of what the node wrote: the tail, the head, a page (offset and limit, at most 500 lines) or only the lines matching a regular expression with context. Reports the total lines and bytes and whether lines were left out. 400 for a bad argument, 404 for an unknown execution or node. ## OpenAPI ````yaml /api/openapi.json get /api/executions/{executionId}/nodes/{nodeId}/output openapi: 3.1.0 info: description: >- Create sessions and workflows, start and steer executions, and read their status, logs and results. Alpha: paths and schemas may change before v0.1.0. title: Yukta REST API version: 0.1.0-alpha.3 servers: [] security: - bearerAuth: [] - apiKeyAuth: [] tags: - description: Supervisors and control planes on the control bus name: Supervisors API - description: List the saved versions and roll back name: Workflow Versions API - description: Endpoints for starting workflows and listing their executions name: Workflow API - description: Edition, licence and features of this build name: Edition API - description: Stop, restart and observe workflow executions name: Execution API - description: Find runs across sessions name: Execution Search API - description: >- Endpoints for control bus operations, node management, and execution observability name: Control Bus & Observability API - description: Who is calling and what the key may do name: Session API - description: Read part of the output of a node name: Node Output API - description: Pause, resume, step and stop nodes name: Execution Control API - description: Endpoints for session and workflow discovery, configuration management name: Session API - description: Validate a draft workflow without saving it name: Session API - description: Workers connected to the control plane name: Workers API - description: Live feed of execution events name: Events API - description: Workflow DAG graph with plugin metadata and per-workflow execution history name: Workflow Details API - description: Follow the result of an execution name: Execution Results API - description: Stream execution logs name: Execution Logs API - description: Control commands and who sent them name: Control audit API - description: Example sessions to start from name: Templates API - description: Signed inbound calls that start a workflow name: Webhook API - description: Check a working directory before creating a session name: Session API - description: Endpoints for discovering workflow plugins name: Plugin API paths: /api/executions/{executionId}/nodes/{nodeId}/output: get: tags: - Node Output API summary: Read part of the output of a node description: >- Returns numbered lines of what the node wrote: the tail, the head, a page (offset and limit, at most 500 lines) or only the lines matching a regular expression with context. Reports the total lines and bytes and whether lines were left out. 400 for a bad argument, 404 for an unknown execution or node. operationId: getOutput parameters: - description: Execution ID in: path name: executionId required: true schema: type: string - description: Node ID in: path name: nodeId required: true schema: type: string - description: stdout, stderr or all in: query name: stream required: false schema: default: all type: string - description: The last N lines in: query name: tail required: false schema: format: int32 type: integer - description: The first N lines in: query name: head required: false schema: format: int32 type: integer - description: First line of a page, 0-based in: query name: offset required: false schema: format: int64 type: integer - description: Page size, default 50, at most 500 in: query name: limit required: false schema: format: int32 type: integer - description: Regular expression the lines must match in: query name: grep required: false schema: type: string - description: Context lines either side of a match, at most 20 in: query name: context required: false schema: format: int32 type: integer responses: '200': content: '*/*': schema: $ref: '#/components/schemas/ApiResponseNodeOutputSlice' description: OK components: schemas: ApiResponseNodeOutputSlice: description: >- Unified API response wrapper for both success and error responses. Success responses include data field; error responses include error, path, and errors fields. properties: data: $ref: '#/components/schemas/NodeOutputSlice' description: The response data error: description: The HTTP status error name example: Bad Request type: string errors: description: The list of field validation errors items: $ref: '#/components/schemas/FieldError' type: array message: description: A human-readable message example: Operation successful type: string path: description: The request path example: /api/files type: string status: description: The HTTP status code example: 200 format: int32 type: integer timestamp: description: The time the response was generated format: date-time type: string type: object NodeOutputSlice: properties: lines: items: $ref: '#/components/schemas/Line' type: array matchedLines: format: int64 type: integer nextOffset: format: int64 type: integer nodeId: type: string stream: type: string totalBytes: format: int64 type: integer totalLines: format: int64 type: integer truncated: type: boolean type: object FieldError: description: Field-specific validation error detail properties: field: description: The name of the field that failed validation example: sessionId type: string message: description: The validation error message explaining the failure example: 'Session not found: ''unknown-session''' type: string type: object Line: properties: number: format: int64 type: integer text: type: string type: object securitySchemes: bearerAuth: scheme: bearer type: http apiKeyAuth: in: header name: X-API-Key type: apiKey ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.