Raisin APIraisin.digital ↗
Search natural wine bars, restaurants, wine shops, winemakers, and events from Raisin.digital. Get geo-filtered venue maps with coordinates and category filters.
What is the Raisin API?
The Raisin.digital API exposes 2 endpoints for searching and mapping the natural wine venues, winemakers, and events listed on Raisin.digital. The search endpoint returns a mixed result set across cities, districts, venues, winemakers, and events matched by keyword, while get_map_venues returns geocoded venue objects filterable by bounding box or city ID, making it straightforward to build location-aware natural wine discovery tools.
curl -X POST 'https://api.parse.bot/scraper/fde4bd63-449d-411a-ba71-42bb4477a710/search' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"lang": "en",
"query": "Paris"
}'Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace raisin-digital-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
from parse_apis.raisin_natural_wine_and_food_guide_api import Raisin, SearchResult, Venue, City, VenueCategory, Lang
raisin = Raisin()
# Search for venues and places matching "Paris" in French
for result in raisin.searchresults.search(query="Paris", lang=Lang.FR):
print(result.name, result.object_type, result.href)
# Get wine bars in Paris using the city constructor
paris = raisin.city(id=2988507)
for venue in paris.venues(category=VenueCategory.BARS):
print(venue.name, venue.latitude, venue.longitude, venue.likevote_number)
Search for places, venues, winemakers, and events by keyword. Returns a mixed list of cities, districts, venues, winemakers, and events matching the query, ordered by relevance. Each result carries an object_type discriminator ('city', 'district', 'venue', 'winemaker', 'event') and fields vary per type. Paginates as a single page.
| Param | Type | Description |
|---|---|---|
| lang | string | Language code for results. |
| queryrequired | string | Search term (place name, country, city, winemaker, event name, etc.) |
{
"type": "object",
"fields": {
"count": "integer total of matching results",
"items": "array of search result objects with varying fields per object_type"
},
"sample": {
"data": {
"count": 31,
"items": [
{
"id": 2988507,
"href": "https://www.raisin.digital/en/explore/france/ile-de-france/paris/",
"name": "Paris",
"region": {
"id": 3012874,
"name": "Ile-de-France",
"object_type": "region"
},
"country": {
"id": 3017382,
"code": "fr",
"name": "France",
"object_type": "country"
},
"object_type": "city",
"object_type_name": "City"
}
]
},
"status": "success"
}
}About the Raisin API
Search Endpoint
The search endpoint accepts a required query string and an optional lang code, returning a count integer and an items array whose objects vary by object_type. A single query can surface cities, districts, venues, winemakers, and events in one response, ordered by relevance. This makes it useful for autocomplete, exploratory search, and resolving human-readable place names to Raisin city IDs that other endpoints can consume.
Map Venues Endpoint
The get_map_venues endpoint retrieves venues suitable for map display. You can scope results either by passing a city_id (obtained from the search endpoint, e.g. 2988507 for Paris) or by supplying a geographic bounding box using the north, south, east, and west decimal-degree parameters — all four bounds are required when city_id is omitted. An optional category parameter narrows results to exactly one of: all, restaurants, bars, wine_shops, accommodations, or winemakers. Each venue object in the response includes id, name, latitude, longitude, likevote_number, comment_number, an is array of type tags, and object_type.
Data Shape and Coverage
Raisin.digital is a curated guide focused on natural wine venues globally. The data reflects the venue listings, winemaker profiles, and events published on that platform. Venue objects carry social signals (likevote_number, comment_number) alongside coordinates, which allows basic ranking by community engagement in addition to geographic filtering.
The Raisin API is a managed, monitored endpoint for raisin.digital — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when raisin.digital changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official raisin.digital API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Build a map of natural wine bars and restaurants in a given city using
get_map_venueswith acity_id. - Autocomplete a location or winemaker search field using keyword results from the
searchendpoint. - Filter natural wine shops within a custom geographic bounding box for a travel itinerary app.
- Rank venues by community engagement using the
likevote_numberandcomment_numberfields. - Resolve a city name to a Raisin city ID via
searchbefore querying map venues for that city. - Aggregate natural wine event listings by querying event
object_typeresults from thesearchendpoint. - Display winemaker profiles alongside nearby venues by combining
searchresults filtered byobject_type.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Raisin.digital offer an official developer API?+
What does the `get_map_venues` endpoint return, and how do I filter by venue type?+
id, name, latitude, longitude, likevote_number, comment_number, an is type-tag array, and object_type. Pass the category parameter with exactly one of all, restaurants, bars, wine_shops, accommodations, or winemakers to narrow the result set.Can I retrieve detailed venue pages — menus, hours, address, or contact details — through this API?+
get_map_venues, plus mixed search results via search. Individual venue detail pages with menus, opening hours, or contact information are not exposed. You can fork this API on Parse and revise it to add an endpoint that fetches those details.What is the difference between using `city_id` and a bounding box in `get_map_venues`?+
city_id returns all venues Raisin.digital associates with that city, regardless of exact coordinate bounds. Passing a bounding box (north, south, east, west) returns venues whose coordinates fall within that geographic rectangle, which is useful for arbitrary or cross-city regions. The two modes are mutually exclusive — use one or the other.Does the `search` endpoint support pagination or return all results at once?+
count and a flat items array in a single response with no documented pagination parameters. For large result sets this means you receive whatever the endpoint returns in one call. You can fork this API on Parse and revise it to add offset or page-based pagination if the underlying data supports it.