tiempoAPI reference
API reference

Conflict previews

Before a shop saves new hours or time off, see which bookings the change would no longer fit, so your rota screen can ask “3 bookings would need moving: save anyway?”. Nothing is changed.

Preview a change

POST/v1/conflict_previews

Send the request you’re about to make (POST or DELETE on /v1/schedules, /v1/schedule_overrides or /v1/blocks, with its id and body) and see what it would do to existing bookings, without making it. It’s checked exactly as the real request would be, so an invalid one gets the same error (body fields named body.…). would_conflict lists the bookings it would leave not fitting, or not fitting differently, with the conflicts they’d have; would_resolve the conflicted ones it would let fit again. Up to 500 of each (has_more). A restricted key needs permission to make the change it previews.

Send the business’s id in Tiempo-Account.

Body parameters

  • methodstringrequired
  • pathstringrequired
  • bodymap

Returns

A conflict preview. Nothing is created, changed or sent.