Your club
Rules a member can read. Turns the engine derives rather than guesses. Pace shown rather than hidden. The club sets the shape of its own week, and everyone can see what the shape is.
Clubs are built with 18 holes over two nines, 27 over three, 36, 45 or 54 over more. The engine plans a day from the club's nines, and the day it plans today is 18 holes or 27, so three nines is the hardest case and the one drawn here. Turn times are derived from the start and the group size, never typed in, and every turn carries the formula it came from.
Tee sheet builder
Tees in play
Loops off each tee
Tees left blank are not part of this rotation.
Rated rotation
Three nines, three tees. The turn allowance is 100 minutes for a 2-ball and 120 for a 4-ball.
Rotation planner
April 2026
Tap a day to paint it. Tap it again to undo.
The member app carries a club theme: the mark, the colours, the greens, the club's name and the words it opens on. On the left is the app in Paralo's own theme. On the right is the same screen under a club's. Both clubs here are invented, and we never show you another club's app.
MC
Tee sheet slots, holding a slot, bookings, member search, competitions, scores, and the webhook events that tell your systems something changed. Pagination and errors are documented too. Your existing software connects through the API and, for clubs whose systems must stay on site, through an on-premise connector.
Endpoints
/v1/clubs/{club}
Objects
Club · Member · Tee sheet · Booking · Course · Competition · Event
List tee sheet slots
$
The ClubOS API reference, drawn as a documentation window rather than served: nothing in it reaches a network. Base URL https://api.paralo.co.uk. Objects: club, member, tee sheet, booking, course, competition, event. Endpoints: GET /v1/clubs/{club}/tee-sheet, list tee sheet slots; POST /v1/clubs/{club}/slots/{slot}/hold, hold a slot; POST /v1/clubs/{club}/bookings, create a booking; DELETE /v1/clubs/{club}/bookings/{booking}, cancel a booking; GET /v1/clubs/{club}/members, search members; GET /v1/clubs/{club}/competitions, list competitions; POST /v1/clubs/{club}/competitions, create a competition; POST /v1/clubs/{club}/competitions/{competition}/scores, submit a score; POST /v1/webhook_endpoints, webhook events. A request is shown as a curl call against the Heathland club, carrying an authorization header and a version header. Lists return an envelope with data and has_more; errors return a type, a stable code, a message and the parameter at fault. Webhook events include booking.created, slot.held, booking.cancelled and four more.
The club sets the shape of its own week, and everyone can see what the shape is.
Your club
Rules a member can read. Turns the engine derives rather than guesses. Pace shown rather than hidden. The club sets the shape of its own week, and everyone can see what the shape is.
Answers to thirty questions clubs ask before they change system
