/stepstone/jobs/search

POST /api/stepstone/jobs/search

Price: 20 credits

Search StepStone job listings by keyword and filters

How to use it

Search StepStone job listings by keyword with rich filters — narrow by location and radius, posting recency, remote-work option, minimum salary, application method, ad language, contract type, full/part-time, required experience, job field, employer sector, region, and city; order by relevance or date. Each result carries the job id, title, hiring company (id, name, logo), location, remote-work flag, a short snippet, and publication date.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• text string required — Search query — job title, skill, or company name (minLength: 1)
• count integer required — Max number of jobs to return (min: 1)
• location string nullable — City name or postal code
• radius integer nullable — Search radius around the location in km (min: 0)
• date_posted string nullable — Restrict to recently posted jobs (one of: "last_24h", "last_7_days")
• work_from_home string nullable — Remote-work option (one of: "full", "partial")
• salary_min integer nullable — Minimum annual salary (min: 0)
• application_method string nullable — How to apply for the job (one of: "company_website", "quick_apply")
• language string nullable — Language of the job ad (one of: "german", "english")
• contract_type string nullable — Type of employment contract (one of: "permanent", "student_job", "temporary", "internship", "thesis", "trainee", "freelance", "apprenticeship", "temporary_employment", "franchise", "sales_agent", "doctorate", "legal_clerkship")
• work_type string nullable — Full-time or part-time (one of: "full_time", "part_time")
• experience string nullable — Required level of experience (one of: "no_experience", "with_experience", "with_management")
• discipline string nullable — Job field / professional category (e.g. IT, Marketing, Finanzen)
• sector_id integer nullable — Employer industry sector id
• region_id integer nullable — Region id
• city_id integer nullable — City id
• sort string nullable — Result ordering (one of: "relevance", "date")

Response

• @type string (default: "StepstoneSearchItem")
• id integer required
• url string required
• company_id integer nullable
• company_name string nullable
• company_url string nullable
• company_image string nullable
• location string nullable
• work_from_home string nullable
• text_snippet string nullable
• is_anonymous boolean nullable
• is_sponsored boolean nullable
• published_at string nullable
• global_id string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.