---
title: "Related Jobs"
method: GET
path: "/landing/related-jobs"
tags: ["landing"]
---

# Related Jobs

`GET /landing/related-jobs`

## Request

- Base URL: `https://api.qarera.com` (the document declares no server; this is the origin it was published from)
- URL: `https://api.qarera.com/landing/related-jobs`
- Auth: none declared

Up to 8 sibling job pages for the on-page 'more jobs' crawl-mesh block,
plus the hub paths this job belongs under.

Same indexable slice as /indexable-jobs (DE/AE, English, <=30d), scoped to
the anchor job's city (country fallback). Served from the in-process hub
snapshot: the per-city SQL this used to run was the query that pinned the
ADB session cap during the Jul 29 crawl wave (each city was its own cache
miss, so one wave = hundreds of concurrent full scans). The snapshot is the
exact same slice, refreshed once per 6h TTL, so the only per-request DB
work left is the anchor's primary-key lookup.

`hubs` rides along here rather than in its own endpoint because the job page
already calls this one — it turns the job-to-job links (a closed loop) into
a real mesh by giving every job page a link back UP to its city, role and
company hubs. Only hubs that clear the publication gate are returned, so a
job page never links to a hub that would 404.

## Query parameters

- `job_id` integer, required

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/qarera/apis/job-copilot-api.md) · [All operations](https://skmtc.dev/qarera/apis/job-copilot-api/llms.txt) · [OpenAPI document](https://skmtc.dev/qarera/apis/job-copilot-api/revisions/cf630251b029?raw)