/superjob/vacancies

POST /api/superjob/vacancies

Price: 1 credit

Get SuperJob vacancy details by id

How to use it

Get full details of a SuperJob (superjob.ru) job vacancy by its id. Returns the job title, salary range with currency and pay period, HTML and plain-text descriptions, key skills, required experience and education, work type, the hiring company (id, name, logo, site, rating), area and region, nearest metro stations with travel time, foreign-language requirements, driver-license categories, employment/schedule/format tags, remote and internship flags, and publication dates.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• vacancy_id string required — SuperJob vacancy id, or a vacancy URL containing it (examples: "27517905", "https://www.superjob.ru/vakansii/servisnyj-inzhener-27517905.html"; minLength: 1)

Response

• @type string (default: "SuperjobVacancy")
• id integer required
• name string required
• url string required
• description string nullable
• description_text string nullable
• salary object nullable
  • @type string (default: "SuperjobSalary")
  • salary_from integer nullable
  • salary_to integer nullable
  • currency string nullable
  • currency_label string nullable
  • period string nullable
  • period_label string nullable
  • is_by_agreement boolean nullable
• company object nullable
  • @type string (default: "SuperjobVacancyCompany")
  • id integer nullable
  • name string nullable
  • image string nullable
  • web_url string nullable
  • vacancy_count integer nullable
  • rating number nullable
  • review_count integer nullable
  • is_redirect boolean nullable
• area_id integer nullable
• area_name string nullable
• region_name string nullable
• metro_stations array (default: [])
  • @type string (default: "SuperjobMetroStation")
  • name string nullable
  • line string nullable
  • line_color string nullable
  • time_to_metro integer nullable
• experience string nullable
• experience_label string nullable
• education string nullable
• education_label string nullable
• work_type string nullable
• work_type_label string nullable
• profession string nullable
• catalogues array (default: [])
• catalogue_ids array (default: [])
• tags array (default: [])
• tag_keys array (default: [])
• key_skills array (default: [])
• languages array (default: [])
• driver_license_types array (default: [])
• is_remote boolean nullable
• is_resume_required boolean nullable
• is_internship boolean nullable
• is_published boolean nullable
• is_archived boolean nullable
• is_closed boolean nullable
• published_at string nullable
• published_till_at string nullable
• created_at string nullable
• updated_at 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 — Vacancy not found or archived 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.