/bayt/companies/jobs

POST /api/bayt/companies/jobs

Price: 10 credits

List the jobs posted by a Bayt.com company across any supported MENA country site, identified by its slug, numeric ID, profile URL or company jobs URL. Results are filtered to the requested company. Each job carries the id, title, url, an AI summary, career level and experience, work setting, citizenship, posting age, hiring company (name, logo, profile), location (district/city/country) and salary range.

How to use it

List a Bayt.com company's job postings by company slug, numeric id, profile URL or company jobs URL. Set country to choose the national site (UAE, Saudi Arabia, Qatar, ...) and language for English or Arabic. Results are filtered to the requested company; each item includes id, title, url, summary, career_level, years_of_experience, is_remote, work_setting, citizenship, is_featured, easy_apply, posted_age, posted_at, 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)
• company string required — Bayt company slug, numeric company ID, a company profile URL, or a company jobs URL (examples: "talabat", "2306165", "https://www.bayt.com/en/company/m-u-e-llc-2306165/"; minLength: 1)
• count integer required — Max number of jobs to return (min: 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: "BaytJobSearchItem")
• 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")
• summary string nullable
• career_level string nullable
• years_of_experience string nullable
• is_remote boolean nullable
• work_setting string nullable
• citizenship string nullable
• is_featured boolean (default: false)
• easy_apply boolean (default: false)
• posted_age string nullable
• posted_at string nullable
• company object nullable
  • @type string (default: "BaytJobSearchCompany")
  • id string nullable
  • name string nullable
  • image string nullable
  • profile_url string nullable
• location object nullable
  • @type string (default: "BaytJobSearchLocation")
  • district string nullable
  • city string nullable
  • country string nullable
• salary object nullable
  • @type string (default: "BaytJobSearchSalary")
  • display string nullable
  • salary_min number nullable
  • salary_max number nullable
  • currency 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 — Company not found, or it currently has no job listings on the selected country site 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.