/habrcareer/experts/search

POST /api/habrcareer/experts/search

Price: 5 credits

Search Habr Career experts (mentors / consultants) by keyword and filters

How to use it

Search Habr Career (career.habr.com) experts — mentors and consultants available for paid sessions — by keyword with filters for qualification level, specializations, and skills. Each result carries the expert username, name, avatar, age, total experience, last job, average score, consulting rate (amount, currency, free-intro flag), qualifications, specializations, skills, and the consulting request topics they accept.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• text string nullable — Search query (name, skill, or keyword)
• count integer required — Max number of experts to return (min: 1)
• qualification string nullable — Qualification level (one of: "Intern", "Junior", "Middle", "Senior", "Lead")
• specialization_ids array nullable — Specialization ids to filter by
• skills array nullable — Skill ids to filter by

Response

• @type string (default: "HabrcareerExpertItem")
• alias string required
• name string required
• url string required
• image string nullable
• age integer nullable
• experience_months integer nullable
• last_job object nullable
  • @type string (default: "HabrcareerResumeJob")
  • position string nullable
  • company string nullable
  • duration string nullable
• last_visited_at string nullable
• score number nullable
• score_count integer nullable
• rate object nullable
  • @type string (default: "HabrcareerExpertRate")
  • amount integer nullable
  • currency string nullable
  • has_free_intro boolean nullable
• qualifications array (default: [])
• specializations array (default: [])
• skills array (default: [])
• requests 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 — 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.