---
title: "Get a Resy restaurant's bookable reservation timeslots"
method: GET
path: "/resy/availability"
tags: ["Resy"]
---

# Get a Resy restaurant's bookable reservation timeslots

`GET /resy/availability`

## Request

- Base URL: `https://api.crawlora.net/api/v1`
- URL: `https://api.crawlora.net/api/v1/resy/availability`
- Auth: API key in header `x-api-key`

Returns the bookable reservation timeslots Resy currently shows for a restaurant, date, and party size -- the same read-only availability an anonymous visitor sees before signing in. The date is optional and defaults to the current date in UTC; the response echoes the date used. This is discovery only; it does not create, hold, modify, or cancel a reservation.

## Query parameters

- `restaurant_id` string, required
- `date` string
- `party_size` integer

## Headers

- `x-api-key` string, required

## Response `200`

OK

- ResyAvailabilityResponseDoc
  - `code` integer
  - `data` ResyAvailabilityResponse
    - `date` string
    - `party_size` integer
    - `restaurant_id` string
    - `timeslots` ResyTimeslot[]
      - `end` string
      - `max_party_size` integer
      - `min_party_size` integer
      - `seating_type` string
      - `start` string: Start/End are Resy's own local "YYYY-MM-DD HH:MM:SS" strings (not RFC3339 -- kept as upstream returns them since seating-area shifts don't carry a UTC offset in the response).
      - `token` string: Token is Resy's opaque reservation-config identifier for this slot (an "rgs://..." string). It is only meaningful back to Resy's own booking flow -- this service does not implement booking, only discovery.
  - `msg` string

## Other responses

- `400`: Bad Request
- `404`: Not Found
- `500`: Internal Server Error
- `503`: Service Unavailable

---

[API](https://skmtc.dev/crawlora/apis/crawlora-api.md) · [All operations](https://skmtc.dev/crawlora/apis/crawlora-api/llms.txt) · [OpenAPI document](https://skmtc.dev/crawlora/apis/crawlora-api/revisions/0497899e2016?raw)