/superjob/vacancies/search

POST /api/superjob/vacancies/search

Price: 20 credits

Search SuperJob vacancies by keyword and filters

How to use it

Search SuperJob (superjob.ru) job vacancies by keyword with rich filters — town/city, region (federal subject), industry catalogue, minimum salary and pay period, employment type, work format, no-experience and internship flags, required driver-license category and foreign language, and publication period; order by relevance, date, or salary. Each result carries the vacancy id, title, salary, hiring company (with rating), area and region, nearest metro, a short requirement 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, keywords, or company name (minLength: 1)
• count integer required — Max number of vacancies to return (min: 1)
• town integer — Town/city id (e.g. 4 = Moscow, 14 = Saint Petersburg) (default: 4)
• subject integer nullable — Region (federal subject) id (see superjob/subjects)
• catalogue integer nullable — Industry/specialization catalogue id
• salary_from integer nullable — Minimum salary (min: 0)
• payment_period string nullable — Salary pay period (one of: "1", "2", "3", "4")
• work_type string nullable — Employment type (one of: "6", "7", "9", "10", "12", "13", "14")
• work_format string nullable — Work location format (one of: "1", "2")
• no_experience boolean nullable — Only vacancies that require no experience
• internship boolean nullable — Only internship vacancies
• driving_license string nullable — Required driver-license category (one of: "A", "B", "C", "D", "E")
• language integer nullable — Required foreign-language id
• period string nullable — Publication period (one of: "1", "3", "7", "0")
• sort string nullable — Result ordering (one of: "relevance", "date_desc", "payment_desc", "payment_asc")

Response

• @type string (default: "SuperjobVacancySearchItem")
• id integer required
• name string required
• url string required
• 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
• profession string nullable
• catalogues array (default: [])
• tags array (default: [])
• tag_keys array (default: [])
• snippet string nullable
• is_remote boolean nullable
• published_at string nullable
• created_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 — 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.