Hotel Bergsonne Allgäu Developer Portal — Booking API, MCP & OpenAPI

This page is the entry point for AI agents, chatbots and integration partners. All read endpoints are public and need no authentication; bookings run through a documented write path.

When to use this API

Query live availability and rates for specific travel dates in Sonthofen, Allgäu.
Describe room types, occupancy, amenities, accessibility and care-room details.
Answer check-in times, contact data and property facts.
Start a direct booking or hand the guest off to the booking flow.

When not to use this API

For other hotels or multi-property search: this API describes Hotel Bergsonne Allgäu only.
For cancelling or changing existing bookings: use email or phone.
For payment processing, guest records or internal systems.
For bulk crawling without a travel intent: a rate limit applies.

Quickstart

Three steps: read property data, check availability, confirm price. All parameters are case-insensitive, all prices in EUR including VAT.

Hotel & room typeshttps://bergsonne-allgaeu.de/api/booking?action=hotel
Availabilityhttps://bergsonne-allgaeu.de/api/booking?action=availability&checkIn=2026-08-20&checkOut=2026-08-23&adults=2
Price quotehttps://bergsonne-allgaeu.de/api/booking?action=price-quote&roomId=KDZ&checkIn=2026-08-20&checkOut=2026-08-23&adults=2
Bookable extrashttps://bergsonne-allgaeu.de/api/booking?action=addons
Create booking (POST)https://bergsonne-allgaeu.de/api/booking?action=bookings

Authentication

Reading is open: hotel, fact-sheet, availability, price-quote, addons and discover-rooms need no token. Writing (action=bookings) uses POST; OAuth 2.1 details are documented at /.well-known/oauth-protected-resource and /.well-known/auth.md.

Scopes & least privilege

Named OAuth scopes are declared machine-readably: as scopes_supported in /.well-known/oauth-protected-resource (RFC 9728) and as an OAuth security scheme in /api/openapi. Agents request only the least scope they need.

hotel:readHotel metadata, room types, amenities, fact sheet, extras
booking:readAvailability, rates, price quotes
booking:writeCreate a reservation for a named human guest

Self-serve registration, no form and no human approval: POST /agent/auth returns an anonymous bearer credential with hotel:read and booking:read. booking:write uses the OAuth flow with PKCE (S256), because a reservation is made on behalf of a named guest.

Sandbox & idempotency

With "test": true in the booking body the request runs in sandbox mode: validation and pricing are identical, no real reservation is created and the response carries a TEST bookingId. An "idempotencyKey" per booking attempt prevents duplicates on retries.

POST https://bergsonne-allgaeu.de/api/booking?action=bookings
Content-Type: application/json

{
  "roomId": "KDZ",
  "rateId": "1",
  "checkIn": "2026-08-20",
  "checkOut": "2026-08-23",
  "adults": 2,
  "customer": {
    "firstName": "Max",
    "lastName": "Mustermann",
    "email": "max@example.com",
    "phone": "+49 170 1234567",
    "country": "DE"
  },
  "idempotencyKey": "8f1c0e2a-...",
  "test": true
}

Errors & rate limits

Errors always return JSON with the fields error, code, hint, docs and openapi. Unknown actions answer HTTP 400 with code UNKNOWN_ACTION, unknown /api/ paths HTTP 404 with code NOT_FOUND. Excessive request rates return HTTP 429 with code RATE_LIMITED.

INVALID_DATESHTTP 400
UNKNOWN_ACTIONHTTP 400
METHOD_NOT_ALLOWEDHTTP 405
FORBIDDEN_ORIGINHTTP 403
NOT_FOUNDHTTP 404
RATE_LIMITEDHTTP 429
UPSTREAM_ERRORHTTP 502

Machine-readable files

Technical contact

Questions about integration, rate limits or write access: email servus@bergsonne-allgaeu.de or call +49 8321 3360.