> ## Documentation Index > Fetch the complete documentation index at: https://docs.eachlabs.ai/llms.txt > Use this file to discover all available pages before exploring further. # Get workflow execution > Retrieve the detail of a single workflow execution: status, inputs, per-step outputs, final output, error, and `total_cost` (the summed cost of the run's model executions). Scoped to the authenticated caller's organization; returns 404 when the execution is missing or owned by another organization. ## OpenAPI ````yaml /openapi_specs/models.json get /v1/workflows/executions/{executionID} openapi: 3.0.3 info: title: each::labs Official API v1 description: > Official each::labs API V1. This API provides access to our comprehensive AI model catalog and other resources. ## Public contract notes - Public API routes handled by request logging include `X-Request-Id` for support and log correlation. Clients may send `X-Request-Id`; otherwise api-service generates one. Root, health, and metrics endpoints are excluded. - REST error bodies keep the backward-compatible JSON shape used by existing clients. Most errors include at least `error`; some shared error paths also include `status` and `details`. Use the HTTP status code as the primary programmatic signal unless an endpoint documents a richer envelope. - Rate-limit and retry headers are endpoint-dependent. If a response includes `Retry-After`, honor it before retrying; otherwise use bounded exponential backoff for retryable 429/5xx responses. version: 1.0.0 contact: name: API Support email: support@eachlabs.ai x-logo: url: ./logo-white.svg altText: each::labs servers: - url: https://api.eachlabs.ai description: Production server security: [] tags: - name: AI Models description: Endpoints for listing and retrieving AI models and other resources. - name: AI Models Prediction description: Endpoints for managing model predictions - name: Uploads description: Endpoints for uploading files that can be used as model inputs. - name: Executions description: Endpoints for listing execution history. - name: Workflows description: >- Endpoints for creating workflows and triggering workflow executions through api-service. - name: OpenAI Compatibility description: OpenAI-compatible endpoints for LLM Router requests. - name: Webhooks description: > Endpoints for retrieving webhook information and delivery history. **Note:** Currently, webhooks are only supported for Workflows V2. We are actively expanding webhook support to other services and will update this documentation as new integrations become available. paths: /v1/workflows/executions/{executionID}: get: tags: - Executions summary: Get workflow execution description: | Retrieve the detail of a single workflow execution: status, inputs, per-step outputs, final output, error, and `total_cost` (the summed cost of the run's model executions). Scoped to the authenticated caller's organization; returns 404 when the execution is missing or owned by another organization. operationId: getWorkflowExecution parameters: - name: executionID in: path required: true schema: type: string description: The workflow execution id. example: b3b1f1a0-0000-0000-0000-000000000000 responses: '200': description: Workflow execution detail content: application/json: schema: type: object properties: execution_id: type: string workflow_id: type: string version_id: type: string description: Workflow version the execution ran against. bulk_id: type: string status: type: string example: completed started_at: type: string format: date-time description: RFC3339 timestamp; omitted until the run starts. completed_at: type: string format: date-time description: RFC3339 timestamp; omitted until the run finishes. inputs: type: object additionalProperties: true step_outputs: type: object additionalProperties: true output: description: Free-form final output (object, array, or scalar). workflow_output: type: object additionalProperties: true error: type: string error_cause: type: string total_cost: type: number format: double nullable: true description: >- Summed cost of the run's model executions. Present only once the execution is terminal (completed/failed/cancelled); omitted while running or if unavailable. '401': $ref: '#/components/responses/Unauthorized' '404': $ref: '#/components/responses/NotFound' '500': $ref: '#/components/responses/InternalServerError' security: - BearerAuth: [] components: responses: Unauthorized: description: Authentication required or invalid credentials headers: X-Request-Id: $ref: '#/components/headers/RequestId' content: application/json: schema: $ref: '#/components/schemas/Error' example: error: Invalid or missing API key NotFound: description: Resource not found headers: X-Request-Id: $ref: '#/components/headers/RequestId' content: application/json: schema: $ref: '#/components/schemas/Error' example: error: 'Failed to fetch model: model not found' InternalServerError: description: Internal server error headers: X-Request-Id: $ref: '#/components/headers/RequestId' content: application/json: schema: $ref: '#/components/schemas/Error' example: error: 'Failed to fetch models: internal error' headers: RequestId: description: >- Request correlation ID. Echoes the incoming `X-Request-Id` header or a generated ID. schema: type: string example: 123e4567-e89b-12d3-a456-426614174000 schemas: Error: type: object description: > Backward-compatible REST error body. Endpoint-specific handlers may return only `error`; shared error paths may also include `status` and `details`. properties: status: type: integer description: HTTP status code, when returned by the shared error handler. example: 400 error: type: string description: Safe user-facing error message. example: error message details: nullable: true description: Optional validation or request details for client errors. required: - error securitySchemes: BearerAuth: type: http scheme: bearer description: >- API key passed as an Authorization Bearer token: `Authorization: Bearer YOUR_API_KEY` ````