/superjob/resumes/search

POST /api/superjob/resumes/search

Price: 20 credits

Browse SuperJob resumes by industry catalogue and filters

How to use it

Browse SuperJob (superjob.ru) candidate resumes within an industry/specialization catalogue, with filters — town, region (federal subject), required experience, age range, gender, maximum expected salary, citizenship, driver-license category, desired employment type, activity period, and photo presence. Each result carries the desired position and salary, area and region, skills, languages, work experience and education, and remote/relocation readiness. Contact details are not included.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• catalogue integer required — Industry/specialization catalogue id to browse resumes for (see superjob/industries) (examples: 48)
• count integer required — Max number of resumes to return (min: 1)
• town integer nullable — Town/city id (e.g. 4 = Moscow, 14 = Saint Petersburg)
• subject integer nullable — Region (federal subject) id (see superjob/subjects)
• experience string nullable — Required work experience (one of: "0", "1", "3", "6")
• age string nullable — Candidate age range (one of: "18-25", "25-35", "35-45", "45-60")
• gender string nullable — Candidate gender (one of: "2", "3")
• salary_to integer nullable — Maximum expected salary (min: 0)
• citizenship integer nullable — Citizenship id
• driving_license string nullable — Required driver-license category (one of: "A", "B", "C", "D", "E")
• work_type string nullable — Desired employment type (one of: "6", "7", "9", "10", "12", "13", "14")
• period string nullable — Candidate activity period (one of: "1", "3", "7", "0")
• with_photo boolean nullable — Only resumes with a photo

Response

• @type string (default: "SuperjobResume")
• id integer required
• url string required
• position string nullable
• salary integer nullable
• salary_currency string nullable
• area_name string nullable
• region_name string nullable
• metro_stations array (default: [])
• gender string nullable
• citizenship string nullable
• marital_status string nullable
• image string nullable
• additional_information string nullable
• key_skills array (default: [])
• languages array (default: [])
• driver_license_types array (default: [])
• catalogues array (default: [])
• experiences array (default: [])
  • @type string (default: "SuperjobResumeExperience")
  • position string nullable
  • responsibility string nullable
  • achievements string nullable
  • date_start string nullable
  • date_end string nullable
  • is_current boolean nullable
  • total_months integer nullable
• educations array (default: [])
  • @type string (default: "SuperjobResumeEducation")
  • level string nullable
  • level_label string nullable
• has_no_experience boolean nullable
• remote_work boolean nullable
• relocate_possibility boolean nullable
• business_trip boolean nullable
• is_volunteer boolean nullable
• created_at string nullable
• updated_at string nullable
• published_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.