/liepin/jobs

POST /api/liepin/jobs

Price: 5 credits

Get one Liepin job posting, a company job or a headhunter job, by URL or by id with kind: title, salary range and months, location and address, experience and education requirements, headcount, full description, publish time, the recruiter, and the hiring company with its registration details.

How to use it

Use to read a full Liepin posting: pass the url from liepin/jobs/search, or its id with its kind. Company and headhunter jobs number their ids separately, so the same id with the other kind is a different posting; a headhunter job names the recruiting firm, not the hiring company.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Liepin job URL, or a job id together with kind (examples: "https://www.liepin.com/job/1985494585.shtml", "https://www.liepin.com/a/79778807.shtml", "85494585"; minLength: 1)
• kind string nullable — Whether the id is a company job or a headhunter job; required with a bare id (one of: "company", "headhunter")

Response

• @type string (default: "LiepinJob")
• id string required
• kind string required (one of: "company", "headhunter")
• url string required
• salary string nullable
• salary_min number nullable
• salary_max number nullable
• salary_months integer nullable
• location string nullable
• city string nullable
• district string nullable
• address string nullable
• work_experience string nullable
• education string nullable
• industry string nullable
• tags array (default: [])
• highlights array (default: [])
• other_requirements array (default: [])
• headcount integer nullable
• description string nullable
• is_promoted boolean nullable
• published_at integer nullable
• refreshed_at integer nullable
• recruiter object nullable
  • @type string (default: "LiepinRecruiter")
  • id string nullable
  • name string nullable
  • image string nullable
  • organization string nullable
  • online_status string nullable
• company object nullable
  • @type string (default: "LiepinJobCompany")
  • id string nullable
  • name string nullable
  • url string nullable
  • image string nullable
  • industry string nullable
  • size string nullable
  • finance_stage string nullable
  • registered_capital string nullable
  • business_scope string nullable
  • description 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 — No job of this kind with this id is published on Liepin, or the job has stopped recruiting 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.