Ambedo HITL lets an agent pause, send context to a reviewer, and resume only after an approve or reject decision. Use it when a workflow is useful to automate but too risky to run unattended.
Your agent calls POST /api/pause with the action and context. It gets back a watchId and status URL.
A human approver receives the request, reviews the context, and approves or rejects it.
The agent polls the status endpoint or receives a webhook and continues based on the decision.
Pause before production deploys, migrations, or risky infrastructure changes.
Review customer emails, DMs, or agent-generated outreach before anything is sent.
Add a decision point before an agent updates records, submits tickets, or changes account data.
If your agent can make HTTP requests, it can use Ambedo HITL. Use the pause endpoint, then either poll for a decision or listen for a webhook.
/api/pauseCreate a pause request
/api/pause/:watchIdCheck approval status
/api/pauseList pauses
/api/pause/:watchId/approveApprove or reject in the dashboard
const res = await fetch("https://hitl.ambedo.dev/api/pause", {
method: "POST",
headers: {
"Authorization": "Bearer hitl_your_api_key",
"Content-Type": "application/json"
},
body: JSON.stringify({
action: "Deploy to production (v2.4.1)",
context: { environment: "prod", commit: "a3f9b2e" }
})
});
const { watchId, statusUrl } = await res.json();
while (true) {
const status = await fetch(statusUrl, {
headers: { "Authorization": "Bearer hitl_your_api_key" }
}).then(r => r.json());
if (status.status !== "pending") {
if (status.status === "approved") continueWithDeploy();
else abortDeploy();
break;
}
await sleep(3000);
}{
"watchId": "wch_a3f9b2e...",
"status": "approved",
"resolvedAt": "2026-03-30T21:00:00.000Z",
"agentContext": {
"action": "Deploy to production (v2.4.1)",
"context": { "environment": "prod", "commit": "a3f9b2e" }
}
}Anything expensive, external, sensitive, or hard to undo: production deploys, outbound messages, data writes, or customer-facing changes.
No. Ambedo HITL is just an API plus a review workflow. If your agent can make an HTTP request, it can use it.
You can poll the status endpoint or receive a webhook when the pause is approved or rejected.