/habrcareer/resumes

POST /api/habrcareer/resumes

Price: 5 credits

Get a Habr Career IT specialist (resume) profile by username

How to use it

Get a Habr Career (career.habr.com) IT specialist / resume profile by username or URL. Returns the candidate name, avatar, specialization, qualification, desired salary, job-search availability, location, age, total experience, relocation readiness, skills, citizenships, foreign languages, an about section, detailed work history (companies with positions and descriptions), university education, and additional education/courses. Direct contacts require an authorized recruiter account and are not returned.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• resume string required — Habr Career specialist username, or a profile URL containing it (examples: "icivilab", "https://career.habr.com/icivilab"; minLength: 1)

Response

• @type string (default: "HabrcareerResume")
• id string required
• name string required
• url string required
• image string nullable
• specialization string nullable
• qualification string nullable
• salary string nullable
• availability string nullable
• location string nullable
• age string nullable
• experience string nullable
• registered_at string nullable
• relocation string nullable
• is_expert boolean nullable
• skills array (default: [])
• divisions array (default: [])
• citizenships array (default: [])
• foreign_languages array (default: [])
• about string nullable
• companies array (default: [])
  • @type string (default: "HabrcareerResumeCompany")
  • location string nullable
  • positions array (default: [])
    • @type string (default: "HabrcareerResumePosition")
    • duration string nullable
    • description string nullable
• education array (default: [])
  • @type string (default: "HabrcareerResumeEducationItem")
  • subtitle string nullable
  • location string nullable
  • courses array (default: [])
    • @type string (default: "HabrcareerResumeEducationCourse")
    • description string nullable
    • duration string nullable
• additional_education array (default: [])
  • @type string (default: "HabrcareerResumeEducationItem")
  • subtitle string nullable
  • location string nullable
  • courses array (default: [])
    • @type string (default: "HabrcareerResumeEducationCourse")
    • description string nullable
    • duration 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 — Specialist profile 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.