/bayt/jobs

POST /api/bayt/jobs

Price: 5 credits

Get full Bayt.com job details by job ID (or job URL) across any supported MENA country site: title, HTML and plain-text description, skills, employment type, posted and expiry dates, salary, hiring company (name, logo, industry, size, profile), location, work setting (remote/hybrid/on-site), number of openings, and preferred-candidate criteria (career level, experience, degree, gender, nationality, residence).

How to use it

Fetch a single Bayt.com job by numeric ID or a job detail URL. Set country to choose the national site (UAE, Saudi Arabia, Qatar, ...) and language for English or Arabic content. Returns one item with id, url, title, description (HTML) and description_text, skills, employment_type, posted_at, valid_through_at, direct_apply, job_location_type, is_remote, total_job_openings, degree, months_of_experience, and preferred-candidate fields (career_level, years_of_experience, gender, nationality, residence_location), plus nested company, location and salary objects.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• job string required — Bayt job ID or a job detail URL containing it (examples: "5465015", "https://www.bayt.com/en/uae/jobs/data-analyst-5465015/"; minLength: 1)
• country string — Bayt country site to query (default: "UAE"; one of: "UAE", "Saudi Arabia", "Qatar", "Kuwait", "Oman", "Bahrain", "Egypt", "Jordan", "Lebanon", "Morocco", "Algeria", "Tunisia", "Libya", "Iraq", "Yemen", "India", "Pakistan", "International")
• language string — Content language (default: "en"; one of: "en", "ar")

Response

• @type string (default: "BaytJob")
• id integer required
• url string nullable
• country string required (one of: "UAE", "Saudi Arabia", "Qatar", "Kuwait", "Oman", "Bahrain", "Egypt", "Jordan", "Lebanon", "Morocco", "Algeria", "Tunisia", "Libya", "Iraq", "Yemen", "India", "Pakistan", "International")
• description string nullable
• description_text string nullable
• skills array (default: [])
• employment_type string nullable
• posted_at string nullable
• valid_through_at string nullable
• direct_apply boolean nullable
• job_location_type string nullable
• is_remote boolean nullable
• total_job_openings integer nullable
• degree string nullable
• months_of_experience integer nullable
• career_level string nullable
• years_of_experience string nullable
• gender string nullable
• nationality string nullable
• residence_location string nullable
• company object nullable
  • @type string (default: "BaytJobCompany")
  • id string nullable
  • name string nullable
  • image string nullable
  • profile_url string nullable
  • industry string nullable
  • size string nullable
• location object nullable
  • @type string (default: "BaytJobLocation")
  • city string nullable
  • country string nullable
  • country_code string nullable
• salary object nullable
  • @type string (default: "BaytJobSalary")
  • display string nullable
  • salary_min number nullable
  • salary_max number nullable
  • currency string nullable
  • unit 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 not found (well-formed but nonexistent or expired listing) 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.