reservations

Reviewed Jan 1, 2000.

• tools: 8 tools scanned
• metadata: scanned

No findings.

Tools (8)

• get_branding

  Get public tenant profile and branding (name, logo, colors, tagline) by the tenant public slug. No API key required.

• list_resources

  List bookable resources of a tenant (rooms, halls, services) by public slug. Optional filters: group_id, search, bed_type, resource_class, min_capacity, amenities (comma-separated). No API key required.

• list_groups

  List resource groups (categories) of a tenant by public slug — only groups with at least one publicly visible resource. No API key required.

• check_availability

  Get free time slots for a resource on a given date. Returns bookable slots considering existing reservations. No API key required.

• create_reservation

  [Requires API key with the matching scope] Create a reservation. Requires an API key with the reservations:write scope; the booking is bound to the key tenant and the resource must belong to it. Provide either check_in_date+check_out_date (overnight/rental) OR start_at+end_at ISO datetimes (time-slot).

• list_reservations

  [Requires API key with the matching scope] List reservations of the API key tenant. Requires the reservations:read scope. Optional filters: resource_id, from/to (YYYY-MM-DD), status, limit (1-200, default 50).

• get_reservation

  [Requires API key with the matching scope] Get a single reservation by its UUID. With the reservations:read scope and matching tenant, returns guest details; otherwise only public status fields.

• cancel_reservation

  [Requires API key with the matching scope] Cancel a reservation by UUID. Requires the reservations:write scope and the reservation must belong to the key tenant (idempotent — cancelling an already-cancelled booking succeeds).