/lagou/jobs

POST /api/lagou/jobs

Price: 5 credits

Get one Lagou job posting by id or URL: title, category, salary range and months, annual salary band, experience and education requirements, full description, work location with coordinates, publish date, the recruiter's name and title, and the hiring company with its products and investors.

How to use it

Use to read a full Lagou posting: pass a job id from lagou/jobs/search or a lagou.com/wn/jobs URL. The recruiter's phone and e-mail are never returned.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Lagou job id or job URL (examples: "11412236", "https://www.lagou.com/wn/jobs/11412236.html"; minLength: 1)

Response

• @type string (default: "LagouJob")
• id string required
• url string required
• full_title string nullable
• category string nullable
• subcategory string nullable
• specialty string nullable
• position_type string nullable
• position_category string nullable
• tags array (default: [])
• skills array (default: [])
• industry_tags array (default: [])
• perks array (default: [])
• salary string nullable
• salary_min number nullable
• salary_max number nullable
• salary_months integer nullable
• annual_salary string nullable
• work_experience string nullable
• education string nullable
• job_nature string nullable
• advantage string nullable
• description string nullable
• description_html string nullable
• department string nullable
• headcount integer nullable
• province string nullable
• city string nullable
• district string nullable
• business_areas array (default: [])
• address string nullable
• latitude number nullable
• longitude number nullable
• subway_line string nullable
• subway_station string nullable
• nearby_stations array (default: [])
• published_at integer nullable
• published_date string nullable
• recruiter_last_login_at integer nullable
• is_campus boolean nullable
• is_expired boolean nullable
• recruiter object nullable
  • @type string (default: "LagouRecruiter")
  • id string required
  • name string nullable
  • image string nullable
• company object nullable
  • @type string (default: "LagouJobCompany")
  • id string required
  • url string required
  • name string nullable
  • short_name string nullable
  • image string nullable
  • size string nullable
  • industry string nullable
  • finance_stage string nullable
  • benefits array (default: [])
  • slogan string nullable
  • website string nullable
  • description string nullable
  • investors string nullable
  • is_verified boolean nullable
  • is_famous boolean nullable
  • products array (default: [])
    • @type string (default: "LagouProduct")
    • name string required
    • url string nullable
    • description string nullable
    • image string nullable
    • types 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 — No job with this id is published on Lagou 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.