AWS Step Functions · Schema
StartSyncExecutionOutput
Amazon Web ServicesiPaaSOrchestrationServerlessWorkflowsState Machines
Properties
| Name | Type | Description |
|---|---|---|
| executionArn | string | The Amazon Resource Name (ARN) that identifies the execution. |
| stateMachineArn | string | The Amazon Resource Name (ARN) that identifies the state machine. |
| name | string | The name of the execution. |
| startDate | string | The date the execution is started. |
| stopDate | string | If the execution has already ended, the date the execution stopped. |
| status | string | The current status of the execution. |
| error | string | The error code of the failure. |
| cause | string | A more detailed explanation of the cause of the failure. |
| input | string | The string that contains the JSON input data of the execution. Length constraints apply to the payload size, and are expressed as bytes in UTF-8 encoding. |
| inputDetails | object | |
| output | string | The JSON output data of the execution. Length constraints apply to the payload size, and are expressed as bytes in UTF-8 encoding. This field is set only if the execution succeeds. If the execution fa |
| outputDetails | object | |
| traceHeader | string | The X-Ray trace header that was passed to the execution. For X-Ray traces, all Amazon Web Services services use the X-Amzn-Trace-Id header from the HTTP request. Using the header is the preferred mech |
| billingDetails | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/aws-step-functions/json-schema/aws-step-functions-start-sync-execution-output-schema.json",
"title": "StartSyncExecutionOutput",
"x-generated": "2026-11-11",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/aws-step-functions-aws-step-functions-api-openapi.yml#/components/schemas/StartSyncExecutionOutput",
"type": "object",
"properties": {
"executionArn": {
"type": "string",
"description": "The Amazon Resource Name (ARN) that identifies the execution."
},
"stateMachineArn": {
"type": "string",
"description": "The Amazon Resource Name (ARN) that identifies the state machine."
},
"name": {
"type": "string",
"description": "The name of the execution."
},
"startDate": {
"type": "string",
"format": "date-time",
"description": "The date the execution is started."
},
"stopDate": {
"type": "string",
"format": "date-time",
"description": "If the execution has already ended, the date the execution stopped."
},
"status": {
"type": "string",
"enum": [
"SUCCEEDED",
"FAILED",
"TIMED_OUT"
],
"description": "The current status of the execution."
},
"error": {
"type": "string",
"description": "The error code of the failure."
},
"cause": {
"type": "string",
"description": "A more detailed explanation of the cause of the failure."
},
"input": {
"type": "string",
"description": "The string that contains the JSON input data of the execution. Length constraints apply to the payload size, and are expressed as bytes in UTF-8 encoding."
},
"inputDetails": {
"$ref": "#/$defs/CloudWatchEventsExecutionDataDetails"
},
"output": {
"type": "string",
"description": "The JSON output data of the execution. Length constraints apply to the payload size, and are expressed as bytes in UTF-8 encoding. This field is set only if the execution succeeds. If the execution fails, this field is null."
},
"outputDetails": {
"$ref": "#/$defs/CloudWatchEventsExecutionDataDetails"
},
"traceHeader": {
"type": "string",
"description": "The X-Ray trace header that was passed to the execution. For X-Ray traces, all Amazon Web Services services use the X-Amzn-Trace-Id header from the HTTP request. Using the header is the preferred mechanism to identify a trace. StartExecution and StartSyncExecution API operations can also use traceHeader from the body of the request payload. If both sources are provided, Step Functions will use the header value (preferred) over the value in the request body."
},
"billingDetails": {
"$ref": "#/$defs/BillingDetails"
}
},
"required": [
"executionArn",
"startDate",
"stopDate",
"status"
],
"$defs": {
"BillingDetails": {
"type": "object",
"properties": {
"billedMemoryUsedInMB": {
"type": "integer",
"description": "Billed memory consumption of your workflow, in MB."
},
"billedDurationInMilliseconds": {
"type": "integer",
"description": "Billed duration of your workflow, in milliseconds."
}
}
},
"CloudWatchEventsExecutionDataDetails": {
"type": "object",
"properties": {
"included": {
"type": "boolean",
"description": "Indicates whether input or output was included in the response. Always true for API calls."
}
}
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/aws-step-functions-start-sync-execution-output"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.