Schedule APIs

These APIs are in beta

The schedule APIs are in beta and may have future breaking changes.

The schedule APIs allow you to manage and interact with schedules within your Omni organization.

Trigger schedule

Triggers the execution of a schedule on demand, outside of its regular schedule.

Basic request

POST /api/unstable/schedules/:scheduleId/trigger

curl -X POST 'https://myorg.omniapp.co/api/unstable/schedules/123e4567-e89b-12d3-a456-426614174000/trigger' \
--H 'Authorization: Bearer <TOKEN>'

Parameters

Note: The scheduleId must be provided as a path parameter.

Parameter	Type	Required	Default	Description
scheduleId	string	Yes ✓	-	The ID of the schedule to trigger. To find a schedule's ID: Navigate to the dashboard of a document. Click File > Deliveries & Alerts. Next to a schedule, click Edit. The schedule's ID is in the page's URL, after /schedules/. For example: https://myorg.omniapp.co/dashboards/e23ebaa0/schedules/123e4567-e89b-12d3-a456-426614174000

Response

200 OK

Successful requests will return a 200 OK status and a response body similar to the following:

{
  "success": true
}

Field	Type	Description
success	boolean	Indicates schedule has been triggered successfully

400 Bad Request

{
  "detail": "<errorReason>",
  "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
  "status": 400
}

Issue	Error detail
Invalid UUID format	Bad Request: scheduleId: Invalid uuid
Invalid method	Invalid method

404 Not Found

{
  "detail": "<errorReason>",
  "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
  "status": 404
}

Issue	Error detail
Schedule not found	Scheduled task with id {scheduleId} does not exist

429 Too Many Requests

Results from too many requests in a given time frame. Refer to the Rate limiting documentation for more information.

500 Internal Server Error

{
  "detail": "<errorReason>",
  "schemas": ["urn:ietf:params:scim:api:messages:2.0:Error"],
  "status": 500
}

Issue	Error detail
Dispatcher error	Various error messages related to dispatch failures