Blocks & own use

You may take your own apartment off the market: for your own stay (owner_stay) or for any other reason (block). That is the whole of what a landlord writes on the calendar — guest bookings, prices and dates of other stays are the agency’s. Both endpoints need landlord:write:blocks.

POST /blocks

curl -X POST https://api.myrentalcalendar.com/partner/v1/landlord/blocks \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{ "unit": "marina-loft-2br", "arrival": "2026-12-20", "departure": "2026-12-27", "type": "owner_stay", "notes": "Family visit" }'

Field	Required	Notes
unit	yes	Slug of one of your current units
arrival / departure	yes	ISO dates, [arrival, departure)
type	no	owner_stay (default) or block
notes	no	Free text the office sees

The block is confirmed immediately, carries no price, and appears on the agency’s calendar like any other stay. Response 201 with the created row in the booking shape.

Refusals

HTTP	code	Meaning
400	VALIDATION	Malformed body, or departure not after arrival
404	NOT_FOUND	Not one of the units you hold today
403	FORBIDDEN	The date lies outside your tenure — e.g. after the effective date of a pending sale
409	BOOKING_CONFLICT	The nights are taken; carries conflict

Check GET /availability first if you want to avoid the 409.

DELETE /blocks/:id

Removes one of your own blocks that has not started yet and releases its nights. Running or past blocks stay as history; guest stays are not yours to touch and answer 404 like anything else that is not your block. Removing twice is not an error — the second call answers 200 too.

HTTP	code	Meaning
200	—	Removed (or already gone)
403	FORBIDDEN	The block is running or in the past
404	NOT_FOUND	No such block of yours

Every block you create or remove is recorded in the agency’s audit trail with your key as the actor.