/incruit/jobs

POST /api/incruit/jobs

Price: 5 credits

Get one Incruit (incruit.com) job posting by number or URL: title, full posting text and images, posting and application dates, employment type, experience, education, salary terms, locations, positions, application methods and documents, benefits and the hiring company

How to use it

Pass an id from incruit/jobs/search.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Incruit job posting number or URL (examples: "2609090002229", "https://job.incruit.com/jobdb_info/jobpost.asp?job=2609090002229"; minLength: 1)

Response

• @type string (default: "IncruitJob")
• id string required
• url string required
• is_headhunting boolean nullable
• text string nullable
• images array (default: [])
• posted_date integer nullable
• application_start_at integer nullable
• application_end_at integer nullable
• deadline_type string nullable
• employment_type string nullable
• employment_types array (default: [])
• experience string nullable
• experience_months integer nullable
• education string nullable
• education_level string nullable
• salary string nullable
• salary_amount number nullable
• salary_period string nullable
• location string nullable
• address string nullable
• postal_code string nullable
• positions array (default: [])
• recruitment_fields array (default: [])
• application_methods array (default: [])
• application_forms string nullable
• required_documents string nullable
• benefits array (default: [])
• company object nullable
  • @type string (default: "IncruitJobCompany")
  • code string nullable
  • name string nullable
  • image string nullable
  • size string nullable
  • industry string nullable
  • address string nullable
  • homepage string nullable
  • founded 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 — Incruit has no job posting under that number 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.