API v1
Everything your systems can ask Quarters.
Published listings and live availability for your website, reservations for whatever runs your contracts or your books, and signed webhooks so none of them has to poll. Small enough to read in a sitting, which is deliberate: this is the whole surface.
- Base URL
https://go.quarters.live/api/v1- Auth
- OAuth 2.0 client credentials, then
Authorization: Bearer. How - Spec
- openapi.json, for Postman, Bruno or a generator.
- Quick start Credentials, a token and your first call, in ten minutes.
- Authentication OAuth 2.0 client credentials. The same grant Guesty uses.
- Webhooks Signed deliveries so nothing has to poll.
- API reference Every endpoint and every object, with samples.
Endpoints
Authentication
Listings
Reservations
Agreements
- GET
/api/v1/reservations/{id}/agreement - PUT
/api/v1/reservations/{id}/agreement - PUT
/api/v1/reservations/{id}/agreement/document - GET
/api/v1/reservations/{id}/agreement/document
Inquiries
First call
A token from the token endpoint, then every published listing.
Request
curl "https://go.quarters.live/api/v1/listings" \
-H "Authorization: Bearer $ACCESS_TOKEN"Recipes
- Build a booking website Mirror the listings, draw the calendar, land the form as an inquiry.
- Sync reservations Load every booking once, then only what changed, for contracts, accounting or a guest portal.
- Contracts signed elsewhere Keep signing in your own system and let Quarters mirror the envelope, the signature and the PDF.