SS APIm.ss.com ↗
Retrieve job vacancies, job-seeker postings, categories, and listing details from SS.com, Latvia's largest classifieds site. 8 endpoints, JSON responses.
What is the SS API?
The SS.com API gives developers structured access to Latvia's most-used classifieds platform across 8 endpoints, covering job vacancy categories, paginated listing results, and full listing detail pages. Starting with get_job_categories to enumerate profession slugs and moving through list_job_listings for paginated vacancy results, each response delivers typed fields including title, company, location, salary, and schedule — ready to ingest without any HTML parsing.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/5a3aaae2-097b-4d7e-804b-d93d9723386e/get_main_categories' \ -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 m-ss-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.
from parse_apis.ss_com_jobs___classifieds_api import SSCom, NotFoundError
client = SSCom()
# Browse top-level site categories
for cat in client.categories.list(limit=5):
print(cat.name, cat.slug)
# List job profession categories with listing counts
for jc in client.jobcategories.list(limit=5):
print(jc.name, jc.count, jc.slug)
# Use constructible JobCategory to list programmer vacancies
programmer = client.jobcategory(slug="programmer")
listing = programmer.listings.list(limit=1).first()
if listing:
print(listing.title, listing.company, listing.location)
# Get full details for that listing
try:
detail = client.joblistingdetails.get(url=listing.url)
print(detail.title, detail.description[:100])
except NotFoundError as exc:
print(f"Listing removed: {exc}")
# Search across the site
for result in client.classifieds.search(query="driver", limit=3):
print(result.title, result.category)
# Browse people seeking work in the programmer category
for seeker in programmer.seekers.list(limit=3):
print(seeker.title, seeker.location, seeker.date)
print("exercised: categories.list / jobcategories.list / listings.list / joblistingdetails.get / classifieds.search / seekers.list")
Retrieve all top-level site categories (Work, Transport, Real Estate, etc.). Each category includes a slug usable for navigation into subcategory endpoints. Returns the full set in one page; no pagination.
No input parameters required.
{
"type": "object",
"fields": {
"categories": "array of category objects with name, url, and slug"
},
"sample": {
"data": {
"categories": [
{
"url": "https://www.ss.com/lv/work/",
"name": "Darbs un bizness",
"slug": "work"
},
{
"url": "https://www.ss.com/lv/transport/",
"name": "Transports",
"slug": "transport"
}
]
},
"status": "success"
}
}About the SS API
Category and Section Navigation
Three endpoints handle the category tree. get_main_categories returns the top-level site sections (Work, Transport, Real Estate, etc.) as an array of objects with name, url, and slug. get_work_section_categories narrows to the Work and Business section, returning subcategories such as vacancies, job-seekers, courses, and services — each with a count field showing live listing volume. get_job_categories (also available as list_all_job_subcategories) returns the full profession taxonomy under the Vakances section, with name, count, URL, and slug per entry. The slug values from these category endpoints feed directly into the listing endpoints as the category parameter.
Vacancy and Job-Seeker Listings
list_job_listings accepts a required category slug and an optional page integer for pagination. Each listing object in the response includes title, url, location, company, schedule, salary, and thumbnail. Salary and schedule fields reflect whatever the poster provided, so they may be absent on individual listings. list_seeking_work_listings mirrors this structure for job-seeker postings, returning title, url, location, and date; the category parameter is optional, so omitting it returns all seeking-work ads across all professions.
Detail and Search
get_job_listing_detail takes a full listing URL (e.g. https://www.ss.com/msg/lv/work/are-required/programmer/xxxxxxx.html) and returns the full description text alongside the title. Response fields vary by listing since SS.com allows free-form ad content. search_jobs accepts a keyword query and returns matching listings with title, url, and category breadcrumb — useful for cross-category searches where the profession slug is unknown.
Coverage and Scope
All endpoints target the Latvian-language ss.com domain. Listing data reflects what posters have published publicly; contact details, phone numbers, and private messaging are not exposed in these endpoints. The category slugs used in list_job_listings and list_seeking_work_listings are consistent with those returned by get_job_categories, making it straightforward to enumerate all professions and iterate through their listings programmatically.
The SS API is a managed, monitored endpoint for m.ss.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when m.ss.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 m.ss.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?+
- Aggregate Latvian job vacancy data by profession category using
get_job_categoriesslugs andlist_job_listings - Monitor listing counts per job category over time using the
countfield fromget_job_categories - Build a job-seeker discovery tool by paginating through
list_seeking_work_listingsfiltered by profession slug - Index full vacancy descriptions for keyword analysis by passing listing URLs to
get_job_listing_detail - Cross-category job search using
search_jobswith occupational keywords like 'programmer' or 'driver' - Map the complete SS.com section hierarchy for navigation or analytics using
get_main_categoriesandget_work_section_categories - Track salary and schedule data availability across listing categories using fields returned by
list_job_listings
| 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.com have an official public developer API?+
What does `get_job_listing_detail` return, and how consistent are the fields?+
get_job_listing_detail returns title and description for the listing at the supplied URL. Because SS.com allows free-form ad content, the structure of the description varies by poster — some ads include salary, schedule, and contact instructions inline; others are brief. There is no guaranteed schema for the description body beyond it being a text string.Can I retrieve listings from SS.com categories outside of jobs, such as real estate or vehicles?+
Does the API expose seller contact information or phone numbers from listings?+
get_job_listing_detail endpoint returns title and description text only. Private contact data behind SS.com's reveal-contact flow is not included in any response. You can fork this API on Parse and revise it to add a contact-detail endpoint if that data is publicly accessible on the listing page.How does pagination work in `list_job_listings` and `list_seeking_work_listings`?+
page integer. The response from list_job_listings includes the page number that was returned alongside the category slug and the listings array. If the page parameter is omitted, the first page is returned. There is no total_pages or total_count field in the response, so iterating requires requesting successive pages until the listings array is empty.