# Tiempo > Tiempo is a scheduling API for booking platforms: resources, working hours, availability search, holds and bookings that never double-book, recurring series, classes with seats, and signed webhooks. One API for every business on your platform, with test and live modes. Scheduling infrastructure for booking platforms. A platform (BookUp, Fresha, a padel club network…) runs many businesses; each business is an account. Within an account you create resources (staff, rooms, courts), give them working hours, search availability, and place bookings: holds that expire, then confirmed. Placement locks resources, so two customers can never both get the last slot. Authenticate with a secret key (tpt_… test, tpk_… live) and send Tiempo-Account: acct_… to act for a business. Every change is an event, delivered to your webhooks signed. ## Docs - [API reference](https://tiempo.one/docs.md): How the Tiempo API works: authentication, acting for a business, test and live modes, requests, versions, errors and webhooks, then every endpoint by topic. ## Guides - [Quickstart: your first booking in 10 minutes](https://tiempo.one/docs/quickstart.md): Create a business, add two barbers with working hours, find open times, hold a slot, confirm it, and watch Tiempo refuse a double booking. curl only. - [Build a booking app with Claude Code, Cursor or Lovable](https://tiempo.one/docs/build-with-ai.md): A rules file and a starter prompt that make your coding agent use Tiempo for availability, holds and bookings instead of writing a fragile scheduler of its own. - [Why AI-built booking apps double-book](https://tiempo.one/docs/double-booking.md): The overlap check a coding agent writes passes every test and still double-books: races, abandoned payments, clock changes, buffers and multi-resource services. What breaks, and what to use instead. - [Testing your integration](https://tiempo.one/docs/testing.md): Test a Tiempo integration before going live: test mode, the dashboard harness, races and holds that expire, idempotent retries, webhooks on your machine, and isolated test data in CI. - [API changelog](https://tiempo.one/docs/changelog.md): Every change to the Tiempo API, newest first: dated versions with breaking changes, plus additions and fixes that apply to every version. - [Salons, barbers and spas](https://tiempo.one/docs/salons-and-barbers.md): Map a salon or barbershop onto Tiempo: staff and chairs as resources, services as segments, any-stylist bookings, buffers, colour with processing time, rotas and time off. - [Classes and group sessions](https://tiempo.one/docs/classes.md): Run classes with a fixed number of places: a session booking with seats, attendees who hold and confirm a place, weekly timetables as series, and waitlists from webhooks. - [Courts, rooms and equipment](https://tiempo.one/docs/courts-and-rooms.md): Book padel and tennis courts, meeting rooms, studios and hire kit: any-court searches on an hourly grid, equipment pools with quantities, maintenance blocks and recurring league slots. - [Chains and multi-location businesses](https://tiempo.one/docs/multi-location.md): Model a chain with several shops: locations with their own timezones, staff who work at different sites on different days, searches per shop, and closing one site without touching the others. ## Comparisons - [Booking engine or calendar scheduling API?](https://tiempo.one/docs/vs-calendar-apis.md): Tiempo compared with Cal.com, Calendly, Nylas and Cronofy: calendar APIs schedule people’s diaries; a booking engine runs many businesses’ staff, rooms, holds and classes. - [Tiempo, Hapio and AvailEngine: headless booking engines compared](https://tiempo.one/docs/vs-headless-engines.md): How Tiempo compares with Hapio and AvailEngine, the other booking APIs for developers: resources, holds that expire, multi-resource bookings, recurring series, and creating businesses by API. - [Square, Microsoft Bookings, Acuity and SimplyBook.me APIs, and Reserve with Google](https://tiempo.one/docs/vs-business-booking-apis.md): The APIs of booking software businesses already use (Square Appointments, Microsoft Bookings, Acuity, SimplyBook.me) compared with building your own platform on Tiempo, plus what Reserve with Google needs. ## Reference - [Accounts API](https://tiempo.one/docs/accounts.md): An account is one business on your platform: a salon, a padel club. - [Locations API](https://tiempo.one/docs/locations.md): A place resources work at, with its own timezone. Locations can be closed with blocks. - [Resources API](https://tiempo.one/docs/resources.md): Anything bookable: a worker, a room, a court. A resource is bookable only inside its schedules: one with none is closed until you give it hours. - [Schedules API](https://tiempo.one/docs/schedules.md): Working hours for one resource, versioned by date. Several weeks make a rotation. Times are local wall-clock, so 09:00 stays 09:00 through daylight saving. - [Schedule overrides API](https://tiempo.one/docs/schedule-overrides.md): Replace one resource’s hours for one local date. An empty list means not working that day. - [Blocks API](https://tiempo.one/docs/blocks.md): Time off, closures, maintenance, lunch. A block targets a resource, a location, or the whole business, for a period or for whole local dates. - [Availability API](https://tiempo.one/docs/availability.md): Ask what can be booked before you show times to a customer. - [Bookings API](https://tiempo.one/docs/bookings.md): Time held on one or more resources. A booking starts pending (a hold that expires after 15 minutes by default) and becomes confirmed when you confirm it. - [Attendees API](https://tiempo.one/docs/attendees.md): A booking with seats is a session (a class, a group). Each attendee takes seats with the same hold-then-confirm flow. Never oversold. - [Series API](https://tiempo.one/docs/series.md): Recurring bookings from an RRULE, created as real bookings over a rolling horizon. A date that doesn’t fit is skipped and reported, not failed. - [Events API](https://tiempo.one/docs/events.md): Every change is an event, written in the same transaction as the change. - [Webhook endpoints API](https://tiempo.one/docs/webhook-endpoints.md): Where Tiempo sends events. One endpoint hears from every business on your platform. - [Usage API](https://tiempo.one/docs/usage.md): Bookings counted towards your bill, per month and per business. Platform-level. ## Optional - [Rules file for coding agents](https://tiempo.one/tiempo-rules.md): drop into a project as AGENTS.md or CLAUDE.md - [OpenAPI description](https://api.tiempo.one/openapi.json): the whole API, machine-readable (OpenAPI 3.1) - [Everything in one file](https://tiempo.one/llms-full.txt): all of the docs above, concatenated