/wttj/jobs/related

POST /api/wttj/jobs/related

Price: 10 credits

List Welcome to the Jungle job postings related to a given job (same profession), excluding the source job. Each result includes the title, summary, contract type, remote policy, salary, profession, sectors, benefits, offices with coordinates, the company and the public job URL.

How to use it

List jobs related to a given Welcome to the Jungle job (matched by profession sub-category). Pass the job URL or '{company_slug}/{job_slug}' and count. Each item has name, summary, contract_type, remote, salary_min/max, profession, sectors, offices, organization_name and url.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Job posting URL or '{company_slug}/{job_slug}' to find related jobs for (examples: "https://www.welcometothejungle.com/en/companies/auchan/jobs/data-analyst-analytic-engineer-en-alternance-f-h_villeneuve-d-ascq", "auchan/data-analyst-analytic-engineer-en-alternance-f-h_villeneuve-d-ascq"; minLength: 1)
• count integer required — Max number of related job postings to return (min: 1)
• language string — Result localization language (default: "en"; one of: "cs", "en", "es", "fr", "sk")

Response

• @type string (default: "WttjJobSearchHit")
• name string nullable
• alias string nullable
• reference string nullable
• wk_reference string nullable
• summary string nullable
• contract_type string nullable
• remote string nullable
• salary_min integer nullable
• salary_max integer nullable
• salary_currency string nullable
• salary_period string nullable
• experience_level_min number nullable
• education_level string nullable
• profession object nullable
  • @type string (default: "WttjProfession")
  • category_name string nullable
  • category_reference string nullable
  • sub_category_name string nullable
  • sub_category_reference string nullable
  • pivot_name string nullable
  • pivot_reference string nullable
• sectors array (default: [])
  • @type string (default: "WttjSectorEntity")
  • name string nullable
  • reference string nullable
  • parent_name string nullable
  • parent_reference string nullable
• key_missions array (default: [])
• benefits array (default: [])
• offices array (default: [])
  • @type string (default: "WttjOffice")
  • address string nullable
  • city string nullable
  • state string nullable
  • district string nullable
  • zip_code string nullable
  • country string nullable
  • country_code string nullable
  • latitude number nullable
  • longitude number nullable
  • is_headquarter boolean nullable
• organization_name string nullable
• organization_alias string nullable
• organization_image string nullable
• published_at string nullable
• 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 — Job posting not found or no related jobs 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.