Endpoint Playground
Test Crawlora's Resy Cuisines API with realistic prefilled parameters. Generate a cURL request, inspect the expected structured JSON response, and open the full docs or pricing page when you are ready to integrate this public web data extraction endpoint into your application.
curl "https://api.crawlora.net/api/v1/resy/cuisines?location=<location>" \
-H "x-api-key: $CRAWLORA_API_KEY"| Parameter | Type | Required | Prefilled value | Description |
|---|---|---|---|---|
| location | string | Yes | Resy location code or numeric id (from a prior resy-search/resy-restaurant response's location_code field) |
{
"code": 200,
"msg": "OK",
"data": {
"location": "ny",
"cuisines": [
"American",
"Chinese",
"Cocktail Bar",
"French",
"Italian",
"Japanese",
"Mediterranean",
"Mexican",
"New American",
"Sushi"
]
}
}Public Playground
Sample responses, schemas, request previews, and code snippets are visible before sign in. Create an account when you are ready to save an API key and run authenticated requests.
Returns the cuisines present among restaurants in a Resy location. Location is a short city code or numeric location id -- both already returned inline as location_code on resy-search and resy-restaurant results; there is no separate closed list of every valid location on Resy's own API, so this value always comes from a prior search/restaurant response rather than a guessed input.
{
"code": 200,
"msg": "OK",
"data": {
"location": "ny",
"cuisines": [
"American",
"Chinese",
"Cocktail Bar",
"French",
"Italian",
"Japanese",
"Mediterranean",
"Mexican",
"New American",
"Sushi"
]
}
}curl "https://api.crawlora.net/api/v1/resy/cuisines?location=<location>" \
-H "x-api-key: $CRAWLORA_API_KEY"