/stepstone/jobs

POST /api/stepstone/jobs

Price: 20 credits

Get StepStone job listing details by id

How to use it

Get full details of a StepStone job listing by its id. Returns the job title, HTML and plain-text descriptions, employment and contract type, work type, industry, salary range with currency and period, the list of job benefits, the hiring employer (id, name, logo, address, website, founding year, industries, employee band, open-job count), the job location with street, postal code and geo coordinates, direct-apply and online flags, application badges, and publication / valid-through dates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — StepStone job listing id, or a job URL containing it (examples: "14128002", "https://www.stepstone.de/stellenangebote--Senior--14128002-inline.html"; minLength: 1)

Response

• @type string (default: "StepstoneJob")
• id integer required
• global_id string nullable
• url string required
• description string required
• description_text string nullable
• employment_type string nullable
• contract_type string nullable
• work_type string nullable
• industry string nullable
• language string nullable
• salary object nullable
  • @type string (default: "StepstoneJobSalary")
  • salary_from integer nullable
  • salary_to integer nullable
  • currency string nullable
  • period string nullable
  • is_predicted boolean nullable
• employer object nullable
  • @type string (default: "StepstoneJobEmployer")
  • id integer nullable
  • name string nullable
  • image string nullable
  • web_url string nullable
  • sector string nullable
  • sector_id integer nullable
  • employee_count string nullable
  • job_count integer nullable
  • address string nullable
  • website string nullable
  • founded integer nullable
  • industries array (default: [])
• location object nullable
  • @type string (default: "StepstoneJobLocation")
  • locality string nullable
  • street string nullable
  • postal_code string nullable
  • country string nullable
  • lat number nullable
  • lng number nullable
• is_direct_apply boolean nullable
• is_online boolean nullable
• published_at string nullable
• valid_through_at string nullable
• benefits array (default: [])
• badges array (default: [])

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 — Job listing not found 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.