/lagou/companies

POST /api/lagou/companies

Price: 5 credits

Get one Lagou company profile by numeric id or URL: name, logo, website, description and photos, industry, size, funding stage, benefits, open job counts, leadership, funding and product history, office addresses with coordinates, and business registration details.

How to use it

Use to profile an employer from a Lagou job: pass company.id from lagou/jobs/search or lagou/jobs. Registration details include the unified social credit code for matching against company registries.

Parameters

• access-token string required

Request body

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

Response

• @type string (default: "LagouCompany")
• id string required
• url string required
• name string nullable
• short_name string nullable
• image string nullable
• website string nullable
• slogan string nullable
• description string nullable
• images array (default: [])
• industry string nullable
• size string nullable
• city string nullable
• finance_stage string nullable
• benefits array (default: [])
• is_verified boolean nullable
• job_count integer nullable
• campus_job_count integer nullable
• resume_process_rate number nullable
• interview_review_count integer nullable
• leaders array (default: [])
  • @type string (default: "LagouLeader")
  • name string required
  • image string nullable
  • description string nullable
  • weibo_url string nullable
  • encyclopedia_url string nullable
• events array (default: [])
  • @type string (default: "LagouCompanyEvent")
  • event_date string nullable
  • category string nullable
  • name string nullable
  • description string nullable
  • url string nullable
  • finance_stage string nullable
  • amount string nullable
• products array (default: [])
  • @type string (default: "LagouProduct")
  • name string required
  • url string nullable
  • description string nullable
  • image string nullable
  • types array (default: [])
• addresses array (default: [])
  • @type string (default: "LagouCompanyAddress")
  • province string nullable
  • city string nullable
  • district string nullable
  • business_area string nullable
  • address string nullable
  • latitude number nullable
  • longitude number nullable
• registration object nullable
  • @type string (default: "LagouCompanyRegistration")
  • legal_name string nullable
  • company_type string nullable
  • established_date string nullable
  • registered_capital string nullable
  • legal_representative string nullable
  • registered_location string nullable
  • credit_code string nullable
  • status string nullable
  • source_url 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 company 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.