Resume a paused Forward Schedule.
Request headers
|
Header |
Required |
Description |
|
|
Yes |
|
|
|
No |
Optional idempotency key for unsafe requests. |
Path parameters
|
Parameter |
Type |
Required |
Description |
|
|
string |
Yes |
Forward Schedule ID. |
Example request
curl -s -X POST 'https://api.qoder.com.cn/api/v1/forward/schedules/sched_019f00112233445566778899aabbccdd/unpause' \
-H "Authorization: Bearer $QODER_PAT"
Example response
HTTP 200 OK
{
"id": "sched_019f00112233445566778899aabbccdd",
"identity_id": "idn_019eabc123",
"template_id": "tmpl_support",
"name": "Daily tech brief",
"status": "active",
"paused_reason": null,
"archived_at": null,
"updated_at": "2026-06-22T12:10:00Z"
}
Response fields
Returns the updated Schedule object with status=active.
Errors
|
HTTP |
Type |
Code |
Trigger |
|
401 |
|
|
PAT invalid or expired. |
|
404 |
|
|
Schedule does not exist. |
|
409 |
|
|
Schedule is archived. |
Notes
-
Unpausing does not create a Schedule Run.
-
The next planned trigger is recalculated from the Schedule trigger policy.