Resume an approval-paused run with approve/deny; streams the continuation over SSE.

Streams text/event-stream. The success body is a sequence of events rather than a JSON document, which is why no 2xx schema is listed below — see Streaming for the event contract.

**Scoped to the calling API-key client:** only a run this client started is reachable — any of its keys, rotations included. Another client's run in the same tenant, a run started before clients were recorded, and another tenant's run are all the same 404 as an unknown id. A team run's assignment approval is a 404 here too: a team run is never started by a client, and its approvals are decided in the Console only.

Request

Path & query

Body

application/json — required, ResumeApprovalRequest

Example

curl -X POST https://api.askamy.co.za/v1/runs/{runId}/approvals/{approvalId} \
  -H "X-Api-Key: $AMY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ … }'

Responses

Schemas