ss APIss.lv ↗
Access real estate listings, spare parts search, and full listing details from ss.lv, Latvia's largest classifieds site, via a structured JSON API.
What is the ss API?
The ss.lv API provides 3 endpoints for extracting structured data from Latvia's largest classifieds platform. Use get_real_estate_listings to pull property listings from specific district-level category paths, search_spare_parts to query transport and automotive parts by keyword with optional price and region filters, and get_listing_detail to retrieve complete details — including description, attributes, and location — for any individual listing URL.
curl -X GET 'https://api.parse.bot/scraper/551d0073-7cc1-4df7-b326-4ee5da9dd679/get_real_estate_listings?category=real-estate%2Fflats%2Friga%2Fcentre' \ -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 ss-lv-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.ss_lv_classifieds_api import SSLv, Listing, ListingDetail, Category
sslv = SSLv()
# Browse real estate in Riga centre via a constructible Category
centre = sslv.category("real-estate/flats/riga/centre")
for listing in centre.listings(limit=5):
print(listing.title, listing.price, listing.url)
# Search spare parts by keyword with price filter
for result in sslv.listings.search(query="bmw", price_max=10000, limit=3):
print(result.title, result.price, result.attributes)
# Navigate from a listing to its full detail
detail = result.details()
print(detail.title, detail.price, detail.location, detail.description)
Fetch real estate listings from a specific leaf-level category path on ss.lv. The category must be a complete path down to a district or sub-category level (e.g., 'real-estate/flats/riga/centre'). Returns up to 30 listings per page with title, URL, price, and column attributes. Non-leaf paths may return empty results.
| Param | Type | Description |
|---|---|---|
| category | string | Category path without /lv/ prefix. Must be a leaf-level path including district (e.g., 'real-estate/flats/riga/centre', 'real-estate/flats/riga/purvciems', 'real-estate/houses-summer-residences/riga/centre'). |
{
"type": "object",
"fields": {
"count": "integer total number of listings returned",
"listings": "array of listing objects each containing title, url, price, and attributes"
},
"sample": {
"data": {
"count": 30,
"listings": [
{
"url": "https://www.ss.lv/msg/lv/real-estate/flats/riga/centre/bfxolh.html",
"price": "550 €/mēn.",
"title": "Īpašnieks izīrē modernu 2 istabu dzīvokli pagalma ēkā ar lielu u",
"attributes": [
"Bruņinieku 73F",
"2",
"70"
]
}
]
},
"status": "success"
}
}About the ss API
Real Estate Listings
The get_real_estate_listings endpoint accepts a category parameter representing a leaf-level path on ss.lv, such as real-estate/flats/riga/centre. The path must extend all the way down to a district or sub-category level — passing a higher-level path like real-estate/flats will return empty results. The response includes a count integer and a listings array where each object carries title, url, price, and an attributes map of additional fields like area, floor, and number of rooms as they appear on the listing card.
Spare Parts Search
The search_spare_parts endpoint accepts a required query string (e.g., bmw, brake pad) and two optional filters: region as a region code string (use '0' for all regions) and price_max as an integer EUR ceiling. Listings priced above price_max are excluded before the response is returned. Results come from the transport/spare-parts category on ss.lv and follow the same count plus listings shape as the real estate endpoint.
Listing Detail
The get_listing_detail endpoint takes a full ss.lv listing URL and returns a single structured object. Response fields include title, price (with currency), location (extracted from listing attributes), description (full text body), and details — a key-value object containing all attribute pairs shown on the listing page, such as make, model, year, condition, or property size depending on the category. This endpoint works for any listing URL on ss.lv, not only real estate or spare parts.
The ss API is a managed, monitored endpoint for ss.lv — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ss.lv 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 ss.lv 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?+
- Track asking prices for Riga centre flats by polling
get_real_estate_listingswith a district-level category path - Build a price-alert tool for car parts by running
search_spare_partswith aprice_maxfilter and comparing results over time - Aggregate multi-district property data by calling
get_real_estate_listingsfor several leaf paths and merging thelistingsarrays - Enrich spare parts search results with full descriptions by piping listing
urlfields fromsearch_spare_partsintoget_listing_detail - Extract structured property attributes (floor, area, rooms) from individual listing pages using the
detailsobject inget_listing_detail - Monitor regional availability of specific spare parts by varying the
regionparameter insearch_spare_partsacross multiple requests
| 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 ss.lv have an official developer API?+
What does `get_real_estate_listings` return and how specific does the category path need to be?+
count and a listings array where each entry has title, url, price, and attributes. The category parameter must reach a leaf level that includes a district or sub-category, for example real-estate/flats/riga/centre. Paths that stop at a higher level — like real-estate/flats — will return empty results because ss.lv paginates data at the district level.