Daylet API (1.0.0)

Returns the configuration of the property the API key is scoped to. Start here: booking_mode tells you whether bookings need room_ids (rooms mode) or not (property mode), payments_enabled whether require_payment: true bookings will work, and deposit_enabled whether those bookings only charge a deposit upfront rather than the full total.

Lists the active rooms of the property (rooms-mode properties only). Use the returned IDs as room_ids when creating bookings, and as room_id when querying availability or quoting. Returns 400 for property-mode properties, which have no rooms.

Lists the active extras (add-on services and items) configured for the property. Use the returned IDs as extras[].extra_id when quoting or creating bookings. Extras with is_required: true are charged and recorded automatically on every booking — only optional extras need to be passed.

Returns unavailable date ranges and booking restrictions for the property within a given window. Use this to pre-validate dates before quoting or creating a booking.

Ranges are half-open [start, end): the end date is checkout-style — the last blocked night is the day before end, and end itself is a valid check-in date.

If the owner keeps a turnover gap between stays, the nights it reserves are returned as their own ranges with source: "gap" — booking and import ranges always name the dates a stay actually runs. Treat every returned range as unbookable regardless of its source.

A gap range can appear without the stay that caused it, when that stay falls outside the window you asked for but the nights it reserves fall inside it. Every range returned overlaps your window, and every night in your window that cannot be booked is covered by one.

Rooms-mode properties must pass room_id (availability is tracked per room); list room IDs with GET /api/v1/rooms.

Blocks ranges of nights (status: "blocked") so guests can't book them, or opens them (status: "open") by removing blocks the owner added. Bookings and stays imported from other calendars are never changed, and blocking a night with a confirmed booking is refused (409).

Unlike the ranges GET returns, these ranges are inclusive at both ends: end_date is the last night, not a check-out date. All ranges are saved together or not at all.

Returns each night's price, status and booking rule between from and to (both inclusive, at most 366 nights), plus the seasons and custom prices overlapping that window. price is what a guest pays for the night before extras, extra-guest charges and discounts — the same figure the dashboard calendar shows.

Unlike GET /api/v1/availability, every range on the prices & availability endpoints is a range of nights with both ends inclusive: end_date is the last night, not a check-out date.

Rooms-mode properties must pass room_id: prices are kept per room.

Sets a custom price on each range of nights, or with price: null removes custom prices so the season or default rate applies again. Custom prices already on those nights are replaced (a longer one is trimmed around them); seasons are left as they are. Where a custom price and a season's price cover the same night, whichever was saved most recently applies.

A fixed price with unit: "week" covers 7 nights: each night costs amount / 7, so a 7-night stay costs exactly amount. A percent price changes the default rate, e.g. -10 for 10% off.

Every range is inclusive at both ends. All ranges are saved together or not at all.

Returns every season, earliest first. A season is a named range of nights with its own price, its own booking rules, or both. A stay follows the booking rules of the season containing its check-in date.

Creates a season with a price, booking rules, or both. Seasons' booking rules can't overlap: creating one whose rules overlap another season's returns 409. rules replace the default booking rules as a whole for arrivals in the season — fields left out take their defaults (no minimum, any day).

Replaces the season's name, dates, price and booking rules with the body. Send the whole season: a price or rules left out is removed. The season's ID may change; use the one returned.

Deletes the season. Its nights go back to the default rate and booking rules, unless a custom price covers them.

Returns the property's seasons, custom prices and blocked dates as CSV text — the same file as the dashboard's Import / export → Download as CSV — with a blank template and a description of the format. Edit the file and send it back to POST /api/v1/rates/csv.

Checks (dry_run: true) or imports a CSV file of seasons, prices and blocked dates. A dry run saves nothing and reports problems line by line, plus what importing would change. Check a file with a dry run first: an import with any problem is refused (422) without saving anything.

An import is all or nothing. Between the first and last date in the file, it replaces the kinds of row the file contains — seasons, prices and/or blocks — so re-sending an edited export does what you expect. rows_replaced says how many existing rows that removes. Bookings and stays imported from other calendars are never changed, and a block over a confirmed booking is refused (409).

Format

One row per date range; the header row is required. Columns: type,name,start_date,end_date,price,price_unit,min_nights,arrival_days,departure_days,weekly_only (and room, for rooms-mode properties)

• type: season (a named period with a price and/or booking rules), price (a price for specific nights) or block (blocked nights).
• name: required for a season; optional note for a block.
• start_date / end_date: first and last night, both inclusive, as YYYY-MM-DD or DD/MM/YYYY.
• price: a number (e.g. 1050 or £1,050), or a change to the default rate like +20% or -10%. Leave empty on a season to keep the default rate.
• price_unit: night or week (a weekly price covers 7 nights). Empty = the unit of the property's base price.
• min_nights, arrival_days, departure_days, weekly_only: booking rules, on season rows only. Days are names separated by | (e.g. Sat or Fri|Sat), in English, French, Spanish or German. weekly_only is yes or no.
• room: the room's name, on every row, for rooms-mode properties. Importing replaces, between the file's first and last date, the kinds of row it contains (seasons, prices and/or blocks). Bookings and dates from other calendars are never changed. Up to 1,000 rows covering up to 3 years.

Returns a server-computed price quote for a prospective stay. Uses the same pricing engine as the guest booking flow, so quotes and real charges never diverge. Returns 422 if pricing is not enabled for the property.

Rooms-mode properties must pass room_id (single room) or room_ids (multi-room stay) — the same rooms you would pass when creating the booking. Required extras are included in the quote automatically.

Optional discount_code previews a discount before booking — final_total already nets it out. Returns 400 if the code doesn't match an active code for this property.

Creates a booking for the property the API key is scoped to.

Bookings created with require_payment: false start as pending and await the owner's approval. With require_payment: true they start as awaiting_payment and are confirmed automatically once Stripe reports the payment.

When require_payment is true, a Stripe Checkout Session is created in the same request and checkout_url is returned — no second round trip needed. Pass success_url and cancel_url to redirect the guest back to your own site after payment.

Rooms-mode properties require room_ids — list them with GET /api/v1/rooms. Optional extras are passed in extras (see GET /api/v1/extras); required extras are recorded and charged automatically. Optional discount_code applies a discount — the request fails with 400 if it doesn't match an active code for this property.

When the property has deposit_enabled (see GET /api/v1/property) and require_payment is true, only the deposit is charged now — the response's deposit_amount, balance_amount, and balance_due_at describe the split, and payment_status is awaiting_deposit rather than awaiting_payment. Both fields are null when the booking isn't on a deposit.

Idempotency

Pass an Idempotency-Key header (any unique string, e.g. a UUID) to make retries safe. The first request for a key is processed and the response stored; later requests with the same key replay the stored response. A 409 is returned if the same key is reused with a different request body.

Returns the details of a single booking. The booking must belong to the property the API key is scoped to — mismatched booking IDs return 404 (not 403) to avoid confirming the existence of another owner's bookings. This is the endpoint for a "view your booking" page: fetch it by the ID returned from POST /bookings whenever the guest returns.

Cancels a booking and notifies the guest by email. Paid bookings are refused with 409 — a cancellation with money involved needs the property owner's refund decision, so it must be done from the Daylet dashboard. Bookings still awaiting_payment can be cancelled; if the guest completes a stale checkout afterwards, the payment is refunded automatically instead of confirming the booking.