/zhaopin/jobs/search

POST /api/zhaopin/jobs/search

Price: 1 credit

Search Zhaopin job postings by keyword, city and filters

How to use it

Search Zhaopin (智联招聘) job postings by keyword, optionally scoped to a city (defaults to nationwide) and refined by salary range, education, work experience, company size, company type, industry, employment nature and result ordering. Returns matching jobs with title, description, salary, required education and experience, work type, listed skills and welfare, job category, headcount, publish date, location and the hiring company.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Search keyword (examples: "python"; minLength: 1)
• city string nullable — City name (Chinese or pinyin, e.g. 北京 / beijing); defaults to nationwide (examples: "北京", "shanghai")
• count integer required — Max number of results (examples: 20; min: 1)
• salary string nullable — Filter by monthly salary range (CNY) (one of: "under_4k", "k4_6k", "k6_8k", "k8_10k", "k10_15k", "k15_25k", "k25_35k", "k35_50k", "over_50k")
• education string nullable — Filter by required education level (one of: "junior_high_and_below", "high_school", "vocational", "junior_college", "bachelor", "master", "mba_emba", "doctorate")
• experience string nullable — Filter by required work experience (one of: "under_1_year", "one_to_three_years", "three_to_five_years", "five_to_ten_years", "over_10_years")
• company_size string nullable — Filter by company headcount (one of: "under_20", "size_20_99", "size_100_299", "size_300_499", "size_500_999", "size_1000_9999", "over_10000")
• company_type string nullable — Filter by company ownership type (one of: "state_owned", "foreign", "joint_venture", "private", "listed", "joint_stock", "public_institution", "other")
• industry string nullable — Filter by company industry (one of: "automotive", "biotech_medical", "electronics_semiconductor", "internet_it", "new_energy", "chemicals_materials", "real_estate_construction", "agriculture", "government_nonprofit", "education", "finance", "media_culture", "logistics_transport", "professional_services", "consumer_services", "manufacturing", "wholesale_retail")
• job_nature string nullable — Filter by employment nature (one of: "full_time", "part_time", "internship", "campus")
• sort string nullable — Result ordering (one of: "smart", "highest_salary", "newest")

Response

• @type string (default: "ZhaopinJob")
• id string required
• url string nullable
• description string nullable
• description_text string nullable
• salary string nullable
• work_type string nullable
• education string nullable
• experience string nullable
• recruit_count integer nullable
• job_category string nullable
• sub_job_type_code string nullable
• skills array (default: [])
• welfare array (default: [])
• published_at string nullable
• company object nullable
  • @type string (default: "ZhaopinJobCompany")
  • name string nullable
  • id string nullable
  • image string nullable
  • size string nullable
  • industry string nullable
  • financing_stage string nullable
  • description string nullable
  • profile_url string nullable
  • best_employer_labels array (default: [])
• location object nullable
  • @type string (default: "ZhaopinJobLocation")
  • city string nullable
  • district string nullable
  • city_id string nullable
  • address string nullable
  • trading_area string nullable
  • latitude number nullable
  • longitude number nullable
• recruiter object nullable
  • @type string (default: "ZhaopinJobRecruiter")
  • name string nullable
  • hr_title string nullable
  • image string nullable
  • online_state 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 — 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.