> ## Documentation Index > Fetch the complete documentation index at: https://docs.lerian.studio/llms.txt > Use this file to discover all available pages before exploring further. # Get Execution Results > Use this endpoint to retrieve the results of a completed workflow execution. The execution must be in a terminal state. ## OpenAPI ````yaml /en/openapi/v3-current/flowker.yaml get /v1/executions/{id}/results openapi: 3.1.0 info: description: >- Complete API reference for Flowker workflow orchestration services including catalog management, workflow definitions, executor configurations, provider configurations, and workflow executions. title: Flowker API version: 1.1.0 servers: - url: https://flowker.sandbox.lerian.net security: - ApiKeyAuth: [] tags: - name: Health API description: Health and version endpoints for monitoring the Flowker service. - name: Catalog API description: >- Browse built-in providers, executors, and triggers available in the Flowker catalog. - name: Workflows API description: >- Create, update, activate, deactivate, clone, and delete workflow definitions. - name: Executions API description: Start workflow executions and track their status and results. - name: Executor Configurations API description: >- Configure, test, and manage external executor connections used by workflow nodes. - name: Provider Configurations API description: Configure, test, enable, and disable provider integrations. - name: Dashboard API description: >- Retrieve aggregated summaries of workflows and executions for operational dashboards. - name: Audit API description: Query and verify audit events for compliance and operational visibility. - name: Webhooks API description: >- Receive webhook callbacks from external systems to trigger workflow executions. paths: /v1/executions/{id}/results: get: tags: - Executions API summary: Get Execution Results description: >- Use this endpoint to retrieve the results of a completed workflow execution. The execution must be in a terminal state. operationId: getExecutionResults parameters: - description: Unique identifier of the execution. in: path name: id required: true schema: format: uuid type: string responses: '200': content: application/json: schema: $ref: '#/components/schemas/ExecutionResultsOutput' description: >- Indicates that the request was successful and the response contains the requested data. '400': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the request was malformed or contained invalid parameters. '404': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: Indicates that the requested resource could not be found. '422': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates that the execution is still in progress and results are not yet available. '500': content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' description: >- Indicates an unexpected internal error. If this persists, please contact support. components: schemas: ExecutionResultsOutput: example: executionId: f7e6d5c4-b3a2-1098-7654-321fedcba098 workflowId: a1b2c3d4-e5f6-7890-abcd-ef1234567890 status: completed stepResults: - stepNumber: 1 stepName: action_log-event nodeId: log-event status: completed output: action: log executedAt: '2026-03-17T14:35:00Z' durationMs: 0 finalOutput: workflow: transactionId: txn-98765 amount: 1500 currency: BRL customerId: cust-12345 message: Payment received startedAt: '2026-03-17T14:35:00Z' completedAt: '2026-03-17T14:35:00Z' properties: completedAt: description: Timestamp when the execution finished. example: '2026-03-17T14:35:12Z' format: date-time type: string executionId: description: Unique identifier of the execution. example: f7e6d5c4-b3a2-1098-7654-321fedcba098 format: uuid type: string finalOutput: additionalProperties: type: object description: Aggregated output from the last step or the workflow's final result. example: workflow: transactionId: txn-98765 amount: 1500 currency: BRL customerId: cust-12345 message: Payment received type: object startedAt: description: Timestamp when the execution started. example: '2026-03-17T14:35:00Z' format: date-time type: string status: description: Final status of the execution. example: completed type: string stepResults: description: Ordered list of results for each step executed. items: $ref: '#/components/schemas/StepResultOutput' type: array workflowId: description: ID of the workflow that was executed. example: a1b2c3d4-e5f6-7890-abcd-ef1234567890 format: uuid type: string type: object ErrorResponse: properties: code: description: Machine-readable error code with the FLK prefix. example: FLK-0001 type: string message: description: Human-readable explanation of the error. example: Invalid input provided type: string title: description: Short error category title. example: Bad Request type: string required: - code - message - title type: object StepResultOutput: properties: durationMs: description: Time taken to execute this step, in milliseconds. example: 0 type: integer errorMessage: description: Error message if the step failed. Null on success. type: string executedAt: description: Timestamp when this step was executed. example: '2026-03-17T14:35:02Z' format: date-time type: string nodeId: description: ID of the workflow node that was executed. example: log-event type: string output: additionalProperties: type: object description: Output data produced by this step. example: action: log type: object status: description: 'Status of this step: `completed`, `failed`, or `skipped`.' example: completed type: string stepName: description: Human-readable name of the step. example: action_log-event type: string stepNumber: description: Position of this step in the execution sequence (1-indexed). example: 1 type: integer type: object securitySchemes: ApiKeyAuth: type: apiKey in: header name: X-API-Key description: >- API key for authenticating requests to the Flowker API. Provisioned via the API_KEY environment variable during deployment. ````