radne-nedjelje APIradne-nedjelje.com ↗
Query stores open on the upcoming Sunday across Croatian areas. Filter by location, brand, and store type. Returns addresses, hours, and distance data.
What is the radne-nedjelje API?
The radne-nedjelje.com API covers two endpoints and returns a structured list of stores open on the upcoming Sunday across selectable Croatian areas. The list_open_stores endpoint accepts a required location slug, optional brand filter, and optional store-type filter, returning per-store fields including address, distance from the area centre, opening hours, and store type. A companion endpoint, list_filter_options, exposes all valid filter vocabularies including area coordinates and known brand slugs.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/0a4d1ad9-d272-4613-888c-92deb82a420e/list_filter_options' \ -H 'X-API-Key: $PARSE_API_KEY'
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 radne-nedjelje-com-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.
"""Walkthrough: find Sunday-open stores in a Croatian area, filtered by type."""
from parse_apis.radne_nedjelje_com_api import RadneNedjelje, StoreType, LocationNotFound
client = RadneNedjelje()
# Fetch the full catalog to discover available areas and the upcoming Sunday date.
catalog = client.catalogs.get()
print("Sunday date:", catalog.sunday_date)
# Pick the first location from the catalog and list its stores.
area = catalog.locations[0]
print(f"Area: {area.name} ({area.location})")
for store in area.stores.list(limit=5):
print(f" {store.store_name} — {store.address} — {store.sunday_hours}")
# Filter to drugstores/cosmetics in the same area.
for store in area.stores.list(store_type=StoreType.DRUGSTORES_COSMETICS, limit=3):
print(f" [drugstore] {store.store_name} ({store.brand}) {store.sunday_hours}")
# Scalar schedule view exposes metadata alongside the store list.
schedule = area.schedule(store_type=StoreType.GROCERIES)
print(f"{schedule.location_name}: {schedule.total} grocery stores on {schedule.sunday_date}")
# Point-lookup by slug with error handling for an unknown area.
try:
remote = client.location("nowhere-land")
remote.stores.list(limit=1).first()
except LocationNotFound:
print("Location not found — use a slug from catalogs.get().locations")
print("exercised: catalogs.get / locations[].stores.list / schedule / location() + LocationNotFound")
Returns the vocabularies used by list_open_stores: every selectable area (slug, display name, centre coordinates), every store brand the site knows (brand slug, display name, and its store type) and the seven store-type codes. Also returns sunday_date, the upcoming Sunday (ISO date, Europe/Zagreb) the site is currently describing. No parameters; one fixed pass over the site's front page and its scripts. Values are taken from the site's own location and brand catalogues, so an area or brand that is absent here does not exist on the site.
No input parameters required.
{
"type": "object",
"fields": {
"brands": "array of known store brands; each has brand (slug accepted by list_open_stores.brands), name, store_type (code) and store_type_label",
"locations": "array of selectable areas; each has location (slug accepted by list_open_stores), name (display label), latitude, longitude (area centre)",
"store_types": "array of the seven store-type codes accepted by list_open_stores.store_type, each with store_type and store_type_label (Croatian label)",
"sunday_date": "ISO date (YYYY-MM-DD) of the upcoming Sunday the store data describes"
},
"sample": {
"data": {
"brands": [
{
"name": "Bakmaz",
"brand": "bakmaz",
"store_type": "namirnice",
"store_type_label": "Namirnice"
},
{
"name": "Bipa",
"brand": "bipa",
"store_type": "drogerije-kozmetika",
"store_type_label": "Drogerije/Kozmetika"
}
],
"locations": [
{
"name": "Zagreb - Centar",
"latitude": 45.815,
"location": "zagreb-centar",
"longitude": 15.9819
},
{
"name": "Split - Zapad",
"latitude": 43.511912,
"location": "split-zapad",
"longitude": 16.427769
}
],
"store_types": [
{
"store_type": "namirnice",
"store_type_label": "Namirnice"
},
{
"store_type": "sport",
"store_type_label": "Sport"
}
],
"sunday_date": "2026-09-13"
},
"status": "success"
}
}About the radne-nedjelje API
What the API Returns
The API surfaces store-opening data for Croatian Sundays (called *radne nedjelje* — working Sundays when retail is permitted). list_open_stores returns one row per physical store for a given area, including store_id, brand, store_name, address, distance_label, distance in metres from the area centre, store type, and the Sunday operating hours. The sunday_date field in every response pins results to a specific upcoming Sunday in ISO format (YYYY-MM-DD), so callers always know which date the data describes.
Filtering and Vocabularies
Before querying list_open_stores, call list_filter_options to retrieve the accepted slugs. It returns three vocabulary arrays: locations (area slugs with display names and latitude/longitude), brands (brand slugs with display names and associated store-type code), and store_types (seven codes with Croatian labels). Pass a single location slug to list_open_stores as the only required parameter. Optionally pass comma-separated brands values (e.g. tommy,bipa) to narrow by chain, or a single store_type code to filter by category. The response includes brands_filter, store_type_filter, and location_name so callers can confirm which filters were applied.
Response Shape and Coverage
list_open_stores returns a total count alongside the stores array, making it straightforward to check result counts before iterating. All area coordinates in list_filter_options reference the centre point used to compute per-store distances, which appear in the distance_label field. Coverage is limited to areas and brands that radne-nedjelje.com tracks; data reflects the single upcoming Sunday the site currently publishes.
The radne-nedjelje API is a managed, monitored endpoint for radne-nedjelje.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when radne-nedjelje.com 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 radne-nedjelje.com 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 Sunday shopping finder app for Croatia that shows nearby open stores by distance from a selected area centre
- Send automated weekly notifications listing which Konzum, Lidl, or Bipa locations are open in a user's chosen area
- Aggregate Sunday retail coverage across multiple Croatian cities by iterating over all slugs from
list_filter_options.locations - Filter open stores by store type (e.g. hypermarket vs. pharmacy) to power category-specific Sunday shopping guides
- Populate a store-brand dropdown in a Croatian retail app using the
brandsvocabulary fromlist_filter_options - Monitor how many stores are open in a given area each Sunday by recording the
totalfield over time
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does radne-nedjelje.com have an official developer API?+
What does list_filter_options return, and do I need to call it every time?+
sunday_date. The vocabularies change infrequently, so you can cache the response and re-fetch only when you need to verify a slug or refresh the Sunday date.Does the API cover historical Sundays or multiple upcoming Sundays?+
sunday_date field. Historical records and multi-week schedules are not currently exposed. You can fork this API on Parse and revise it to add date-range or historical endpoints if your use case requires them.Can I filter list_open_stores by multiple store types at once?+
store_type parameter accepts a single store-type code per request. Filtering by multiple types simultaneously is not currently supported. The API does accept comma-separated values for the brands parameter, so multi-brand filtering is available. You can fork the API on Parse and revise it to support multi-value store-type filtering.Are store coordinates (latitude/longitude) returned for individual stores?+
stores array. The list_filter_options endpoint does return latitude and longitude for each area centre, which is what the per-store distance_label and distance-in-metres fields are measured against. You can fork this API on Parse and revise it to surface individual store coordinates if the source exposes them.