AI integrations
Control agent job
Pause, resume, approve, reject, or schedule an agent job.
POST
Use this endpoint to pause or resume a running job, approve or reject a waiting checkpoint, or promote a finished plan into a one-time or recurring schedule.
Pause, resume, approve, and reject return a job status object. Schedule actions return a smaller payload with the new child job or recurring template.
Authorization
Blnk Cloud APIs support any one of the following authentication methods. All of them work with yourCLOUD_API_KEY or OAUTH_ACCESS_TOKEN.
- Bearer token
- X-Blnk-Key header
- X-API-Key header
Path
string
required
Job to control (
job_...). Use the job_id returned by Create agent job.Body
string
required
What to do with the job:
pause: Soft pause. The current step finishes, then the job and its plan run stop before the next step. Status becomespaused.resume: Start the job again. Ifscheduled_run_atis still in the future, status returns toscheduled. Otherwise Cloud runs it now.approve: Continue a job inwaiting_approval. The job must already have aplan_run_id.reject: Fail the waiting step and move the job tofailed. The job must already have aplan_run_id.schedule: Create a one-time child job or a recurring template from this job’s plan. The job must already have a reusable plan.
string
Who approved or rejected the waiting step. Required in practice for an audit trail. If you omit it, Cloud stores
job-control. Used only with approve and reject.string
Why you approved or rejected the step. Stored with the decision. Used only with
approve and reject.string
Required when
action is schedule.once: creates a child job that runs atrun_at.recurring: creates a template that keeps using this job’s plan.
string
When the child job should start. Required for
mode: "once". Send an RFC3339 timestamp such as 2026-09-17T09:00:00Z.string
How often the recurring template should run. Required for
mode: "recurring", e.g. 0 * * * * for every hour.string
Timezone for the cron expression. Defaults to
UTC. Use an IANA name such as Africa/Lagos.string
Label for the recurring template. If you omit it, Cloud uses a truncated copy of the original job message.
Response
Pause, resume, approve, and reject return the job after the action. Schedule returns a smaller payload for the new child job or template.string
Job you sent in the path (
job_...). On schedule actions this is the parent job, not the new child or template.string
After pause:
paused. After resume or approve: usually running. After reject: failed. After schedule once: scheduled (the child job). After schedule recurring: active (the template).string
Short sentence that matches
status. Present on pause, resume, approve, and reject. Not on schedule responses.string
Plan attached to the job (
pr_...). Present on pause, resume, approve, and reject.string
Why the job failed. Present after
reject, or when a step already failed.array
Plan steps on the job. Present on pause, resume, approve, and reject. This is the raw step list, not the compact status view.
timestamp
When Cloud accepted the job. Present on pause, resume, approve, and reject.
timestamp
When the control action landed. Present on pause, resume, approve, and reject.
string
New child job created by
schedule + once (job_...). Poll this ID with Get job status.timestamp
When that child job will start, in UTC ISO 8601. Only on
schedule + once.string
Template created by
schedule + recurring (rt_...).timestamp
When that template will fire next, in UTC ISO 8601. Only on
schedule + recurring.