Skip to main content
POST /api/v1/forward/schedules/{schedule_id}/pause Pauses a Schedule. Paused schedules do not run on trigger policy and cannot be manually run.

​
Headers

HeaderRequiredDescription
AuthorizationYesBearer <PAT>
Content-TypeNoapplication/json if a body is sent.
Idempotency-KeyNoOptional idempotency key for unsafe requests.

​
Path parameters

ParameterTypeRequiredDescription
schedule_idstringYesForward Schedule ID.

​
Example request

curl -s -X POST 'https://api.qoder.com/api/v1/forward/schedules/sched_019f00112233445566778899aabbccdd/pause' \
  -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": "paused",
  "paused_reason": {
    "type": "manual"
  },
  "archived_at": null,
  "updated_at": "2026-06-22T12:00:00Z"
}

​
Response fields

Returns the updated Schedule object with status=paused.

​
Errors

HTTPTypeCodeTrigger
401authentication_errorauthentication_requiredPAT invalid or expired.
404not_found_errorschedule_not_foundSchedule does not exist.
409invalid_request_errorschedule_archivedSchedule is archived.

​
Notes

  • The body may be omitted or an empty JSON object {}.
  • Current design only exposes manual pause reasons.

Unpause a schedule

Run a schedule