Skip to main content
POST
/
v3
/
agents
/
{agent_key}
/
schedules
/
{schedule_id}
/
execution
curl -X POST https://api.orq.ai/v3/agents/customer_digest/schedules/01KPN29WWKSK0VDPJNTKZPVNRB/execution \
  -H "Authorization: Bearer $ORQ_API_KEY"

{
  "status": "triggered",
  "schedule_id": "01KPN29WWKSK0VDPJNTKZPVNRB"
}
Runs the schedule’s payload immediately (≈10 seconds after the request, to stay above the NATS scheduler’s minimum deliver-at margin). The schedule’s regular cadence is unaffected — useful for smoke-testing a new schedule, UI “Run now” buttons, or manually re-running a missed execution. Inactive schedules return 400 schedule_inactive. The run appears in traces as a schedule.<agent_key> leading span — same structure as an HTTP-invoked run. See Agent Schedules. 
curl -X POST https://api.orq.ai/v3/agents/customer_digest/schedules/01KPN29WWKSK0VDPJNTKZPVNRB/execution \
  -H "Authorization: Bearer $ORQ_API_KEY"

{
  "status": "triggered",
  "schedule_id": "01KPN29WWKSK0VDPJNTKZPVNRB"
}

Authorizations

​
Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

​
agent_key
string
required

The unique routing key of the agent the schedule belongs to.

​
schedule_id
string
required

The schedule's ULID, as returned from create.

Response

Execution scheduled for immediate delivery.

​
schedule_id
string
required
​
status
string
required

Always "triggered" on success.