Shelly

Developer portal

Shelly Restaurant developers

The public API behind shellyrestaurant.com.au: live availability for the dining experiences, published guest reviews, and a contact channel. It backs the booking forms on this site, so it returns exactly what a guest sees.

Authentication and sandbox

None needed. Every endpoint is read only (the one write, POST /api/contact, sends a message to a human), so there are no API keys, no OAuth, and no separate sandbox — production is safe to call directly. Requests are rate limited to 60 per minute per IP, with X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset headers on every response, and CORS is open.

Quickstart

# Which nights is Trust Rony running, and what is sold out?
curl "https://www.shellyrestaurant.com.au/api/experience-dates?slug=trust-rony"

# Latest published guest reviews
curl "https://www.shellyrestaurant.com.au/api/reviews-list?per_page=5&sort=newest"

# The full API specification
curl "https://www.shellyrestaurant.com.au/openapi.json"

OpenAPI specification

The full machine readable contract — every operation with typed parameters, response schemas, and error shapes — is published at /openapi.json (OpenAPI 3.1, also served at /api/openapi.json). Errors are JSON: unknown API paths return a structured 404 with an error.code and a resolution hint, never an HTML page.

Endpoints

  • GET /api/experience-dates

    Bookable nights for one experience (slug: 4-seasons, trust-rony, four-elements, kids), with per seating labels, sold out flags, and seats remaining once a night is nearly full.

  • GET /api/reviews-list

    Published Google reviews for Shelly and Shelanous, paginated; filter by venue, rating, or text; sort by newest, oldest, or top.

  • POST /api/contact

    Send a general enquiry to the team (name, email, phone, message). Not for reservations.

  • GET /api/health

    Aggregate service health for uptime checks; 503 when degraded.

  • GET /api

    Machine readable directory of everything on this page.

MCP server

The same data is exposed as Model Context Protocol tools over Streamable HTTP at https://www.shellyrestaurant.com.au/api/mcp, discoverable at /.well-known/mcp. Point any MCP client at it — no session setup, read only.

For AI agents

Agent oriented resources — llms.txt, Markdown content negotiation for every page, and when-to-use guidance — are indexed on the agents page.

Contact

Technical or data questions: info@shellyrestaurant.com.au.