---
title: "Get a Resy ticketed dining event's full description and ticket packages"
method: GET
path: "/resy/event"
tags: ["Resy"]
---

# Get a Resy ticketed dining event's full description and ticket packages

`GET /resy/event`

## Request

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

Returns a ticketed dining event's full description, event-day instructions, and per-ticket-tier package breakdown (price, what's included, live ticket availability). All three identifiers come from a prior resy-events result: event_url_slug is that result's url_slug, restaurant_url_slug is its restaurant_url_slug, and location is the same city identifier resy-events was called with. Read-only discovery -- does not purchase a ticket.

## Query parameters

- `event_url_slug` string, required
- `restaurant_url_slug` string, required
- `location` string, required
- `party_size` integer

## Headers

- `x-api-key` string, required

## Response `200`

OK

- ResyEventDetailResponseDoc
  - `code` integer
  - `data` ResyEventDetailResponse
    - `currency` string
    - `date` string
    - `description` string
    - `end_time` string
    - `enhanced_description` string
    - `enhanced_need_to_know` string
    - `general_sale_date` string
    - `images` string[]
    - `is_presale` boolean
    - `max_party_size` integer
    - `min_party_size` integer
    - `name` string
    - `need_to_know` string
    - `packages` ResyEventPackage[]
      - `max_party_size` integer
      - `min_party_size` integer
      - `name` string
      - `price_total` number
      - `price_total_str` string
      - `quantity_remaining` integer
      - `quantity_total` integer
      - `sold_out` boolean
      - `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.
      - `whats_included` string[]
    - `price_max` number
    - `price_min` number
    - `shift_id` integer
    - `time` string
    - `url_slug` string
  - `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)