Difference between revisions of "API schedules"
From Charitylog Manual
| Line 6: | Line 6: | ||
If you want to use this endpoint for your own time and attendance solution, these calls may help: | If you want to use this endpoint for your own time and attendance solution, these calls may help: | ||
| + | |||
| + | All jobs in a date range, with an id and completion status: | ||
| + | [GET] https<nowiki/>://api.dizions.co.uk/v2/schedules/date_active/2021-04-01,2021-04-30/field/id;status | ||
| + | |||
| + | Jobs with for worker 220 in a date range, with an id and completion status: | ||
| + | [GET] https<nowiki/>://api.dizions.co.uk/v2/schedules/worker/220/date_active/2017-04-01,2017-04-31/field/id;status | ||
Revision as of 17:06, 12 February 2021
These are Roster job cards.
NB, this endpoint cannot currently be used for schedule creation, which is only possible using the Confirm Work Schedules option in the web app. This is because this endpoint is primarily intended for our mobile roster app, Call Round, which gets lists of jobs and updates them, typically to complete or cancel them.
If you want to use this endpoint for your own time and attendance solution, these calls may help:
All jobs in a date range, with an id and completion status:
[GET] https://api.dizions.co.uk/v2/schedules/date_active/2021-04-01,2021-04-30/field/id;status
Jobs with for worker 220 in a date range, with an id and completion status:
[GET] https://api.dizions.co.uk/v2/schedules/worker/220/date_active/2017-04-01,2017-04-31/field/id;status
