An API your integrations already know.

129 endpoints at api.rotatree.com/v1 that use RotaCloud’s paths, parameter names, numeric IDs and pagination.

curl 'https://api.rotatree.com/v1/shifts?start=1798761600&end=1799366400&limit=100&offset=0' \
  -H "Authorization: Bearer $ROTATREE_API_KEY"

# 120 requests per minute per key
# limit and offset pagination, numeric IDs, Unix-second timestamps

Endpoints

Same paths, same parameter names

Shifts, users, locations, roles, leave, attendance, availability and more, with RotaCloud’s documented query and body parameter names, numeric IDs and Unix-second timestamps.

  • Base URL https://api.rotatree.com/v1
  • limit and offset pagination
  • Numeric public IDs
  • OpenAPI spec at api.rotatree.com/openapi.json
curl 'https://api.rotatree.com/v1/shifts?start=1798761600&end=1799366400&limit=100&offset=0' \
  -H "Authorization: Bearer $ROTATREE_API_KEY"

# 120 requests per minute per key
# limit and offset pagination, numeric IDs, Unix-second timestamps

Keys

Admin keys you can revoke

Admins create named API keys in Settings. The key is shown once; only a hash is stored. Revoke a key and it stops working.

  • Administrator-only key management
  • Keys stored hashed
  • 120 requests per minute per key, then 429 with Retry-After
  • Optional User header to act as one user
API access settings showing the API address, specification downloads and a Create key form

Webhooks

Signed webhooks for shift events

Register an endpoint and RotaTree posts shift changes to it. Every delivery is signed so you can verify where it came from.

  • Shift events: created, updated, deleted, claimed, acknowledged
  • v1 and v2 webhook formats
  • Signed deliveries
# Verify the signature header before trusting the body
# Respond 2xx to acknowledge

Import and export

RotaCloud import, CSV out

Moving from RotaCloud? The RotaTree team imports your shifts, workers, locations and roles for you and keeps their source IDs. Rotas, leave and attendance export to CSV.

  • Source IDs preserved
  • Import run with you by the RotaTree team
  • CSV exports
Your team table listing each person with their role, location and pay rate

Compatibility means the same 129 method and path combinations and the documented parameter names. We do not claim identical behaviour in every case. Payroll calculation and document signing endpoints are registered but return 501 (not implemented). RotaCloud keys do not authenticate to RotaTree; create a RotaTree key. Check the OpenAPI spec for the detail.

FAQs

Is it a drop-in replacement for the RotaCloud API?

It registers the same 129 method and path combinations and keeps the documented parameter names, so most integrations need only a new base URL and key. We do not claim identical behaviour in every case, and payroll calculation and document signing return 501. Test against the OpenAPI spec.

How do I authenticate?

Send the key as a Bearer token in the Authorization header. Keys are created by an admin in Settings.

What is the rate limit?

120 requests per minute per key. Beyond that the API returns 429 with a Retry-After header.

Which events do webhooks deliver?

Shift events: created, updated, deleted, claimed and acknowledged.

Can a key see other companies’ data?

No. The company comes from the key, never from the request.

How do we get a demo?

Tell us how big the team is. We will show you RotaTree set up for a team like yours.

  • Weekly rota
  • Monthly rota
  • Open shifts
  • Copy week
  • Draft to publish
  • Labour cost per day
  • Leave ledger
  • Sickness and TOIL
  • Availability patterns
  • 20-second QR clock-in
  • Monthly attendance sheet
  • Payroll lock
  • Scheduled vs actual
  • CSV export
  • API
  • Signed webhooks
  • Multi-location
  • Pay rates
  • Weekly-hour limits