Build a Scheduling Portal Integration
Use CRD endpoints to find existing schedules, start runs, and track results.
Recommended flow
Authenticate using the token operation configured for your CRD deployment.
Browse folders with /api/Folder/Get, /api/Folder/GetSubFolders, and /api/Folder/GetSchedules, or resolve a schedule path with /api/Folder/GetUniqueIdFromPath.
Show the schedule name and type returned by CRD. Keep its schedule type and UniqueId together when identifying it.
When a user requests a run, submit POST /api/Schedule/ExecuteScheduleAsync and retain the returned ExecutionId.
Use GET /api/Schedule/GetExecutionStatus to display the returned execution status. Use GET /api/Schedule/GetExecutionQueue to show queue records.
Protect access and identifiers
Keep schedule IDs, execution IDs, and process IDs distinct. Protect credentials and bearer tokens in the portal. Apply the access controls configured for your CRD service when displaying schedules or allowing users to run them.
See the API Reference for request and response models.
Updated about 3 hours ago