On-call schedules

Hand duty over temporarily

Puts somebody else on duty for a window without editing the rotation: the resolver consults handovers before shifts, so when the window ends the original person resumes on their own and nothing has to be restored. Who is being covered for is captured at creation time and reported as replacing. Not idempotent — repeating the call creates a second handover, and the later-starting one wins where they overlap. The window may not exceed 30 days.

post/api/v1/schedules/{schedule}/overrides

Request

  • Base URL: https://wardenpoint.com (the document declares no server; this is the origin it was published from)
  • URL: https://wardenpoint.com/api/v1/schedules/{schedule}/overrides
  • Auth: API key in header X-API-Key

Path parameters

schedulestring uuid required

Schedule UUID.

Request body

role'primary' | 'secondary' | 'manager' required

Which slot of the rotation is handed over.

recipient_uuidstring uuid required

Who stands in. Must be a recipient of this company.

starts_atstring date-time required

ISO-8601 WITH an explicit offset ("2026-08-10T09:00:00Z" or "2026-08-10T09:00:00+02:00"). A value without an offset is rejected with 422: it would otherwise be read in the platform timezone and land hours away from what you meant.

ends_atstring date-time required

ISO-8601 with an explicit offset. Must be after starts_at and no more than 30 days later.

reasonstring nullable

Why the handover happens, in your own words — shown beside it on the schedule page so the next person to look does not have to ask. Nothing is matched or routed on it, and it is not sent to the stand-in.

Response

The handover.

Changes

No recorded changes to this operation across all 1 revision of this API.