API Reference
Read one workflow run
Stands on its own, outside /workflows/{id}/executions, and is guarded by the same automation:read scope.
Try it — GET /executions/{id}
Kept for this tab only — it disappears when you close it, and it is never sent anywhere except as the Authorization header on the call below.
Authorization
bearerAuth automation:readAuthorizationBearer <token>
Authorization: Bearer sk_live_.... Keys in the query string or the
request body are refused — a URL is logged by every proxy it passes,
and that is how customer keys leak.
A key carries scopes. A call outside them answers 403 with
insufficient_scope and names the scope it wanted.
In: header
Scope: automation:read
Path Parameters
id*string
The prefixed id of the object.
Response Body
application/json
application/json
application/json
application/json
application/json
curl -X GET https://app.sendkuy.com/api/v1/executions/exe_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3 \ -H "Authorization: Bearer sk_live_YOUR_API_KEY"{ "data": { "object": "workflow_execution", "id": "exe_9cBe3A1H-SLhW5fONWZ32wb-IIio5Ts3", "workflow_id": "string", "contact_id": "string", "status": "string", "started_at": "2019-08-24T14:15:22Z", "completed_at": "2019-08-24T14:15:22Z", "error": "string", "created_at": "2019-08-24T14:15:22Z", "updated_at": "2019-08-24T14:15:22Z" }}