/jooble/jobs/search

POST /api/jooble/jobs/search

Price: 20 credits

Search Jooble jobs by keyword, location, and filters

How to use it

Search Jooble job listings by keyword and location across country editions, with filters for posting date, employment type, search radius or location mode, minimum salary (by pay period), required experience, and whether a salary is disclosed. Each result carries the job id, title, the apply/source URL, posting date (relative caption and ISO update date), a short snippet and the full job description, salary (display string plus parsed from/to amount, period and currency), the hiring company (name, logo, page, verification flags), location with coordinates, employment/condition tags, the source site logo, and a set of status flags.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• keyword string required — Job search keyword or title (minLength: 1)
• count integer required — Max number of jobs to return (min: 1)
• location string nullable — City, region, or address to search in
• country string — Jooble country edition to search (default: "US"; one of: "US", "GB", "CA", "IE", "IN", "AU", "NZ", "DE", "FR", "ES", "IT", "NL", "AT", "BE", "CH", "PT", "SE", "NO", "DK", "FI", "PL", "CZ", "HU", "RO", "GR", "UA", "TR", "AE", "ZA", "SG", "MY", "ID", "BR", "MX", "AR", "CL", "CO")
• radius string nullable — Location matching mode or search radius (one of: "near_me", "remote", "exact", "within_3mi", "within_5mi", "within_11mi", "within_15mi", "within_25mi", "within_50mi")
• date_posted string nullable — Restrict to jobs posted within this period (one of: "all_time", "last_24_hours", "last_3_days", "last_7_days")
• job_type array nullable — Employment types to include (one of: "full_time", "temporary", "part_time")
• min_salary integer nullable — Minimum salary, expressed in the units of salary_rate (min: 0)
• salary_rate string — Pay period that min_salary is measured in (default: "yearly"; one of: "hourly", "monthly", "yearly")
• experience string nullable — Required work experience level (one of: "any", "internship")
• with_salary boolean nullable — Only return jobs that disclose a salary

Response

• @type string (default: "JoobleJob")
• id string required
• url string nullable
• date_caption string nullable
• updated_at string nullable
• snippet string nullable
• description string nullable
• salary object nullable
  • @type string (default: "JoobleJobSalary")
  • display string nullable
  • salary_from number nullable
  • salary_to number nullable
  • period string nullable
  • currency string nullable
• estimated_salary string nullable
• company object nullable
  • @type string (default: "JoobleCompany")
  • name string nullable
  • company_url string nullable
  • image string nullable
  • is_verified boolean nullable
  • is_contacts_verified boolean nullable
  • has_hires boolean nullable
  • has_many_hires boolean nullable
  • is_active_responses boolean nullable
• location object nullable
  • @type string (default: "JoobleLocation")
  • name string nullable
  • latitude number nullable
  • longitude number nullable
  • is_shift_job boolean nullable
  • is_walking_distance boolean nullable
• tags array (default: [])
  • @type string (default: "JoobleTag")
  • name string nullable
  • text string nullable
  • category string nullable
• highlight_tags array (default: [])
• source_logo string nullable
• applies_count integer nullable
• job_type string nullable
• region_id integer nullable
• similar_group_id string nullable
• is_new boolean nullable
• is_premium boolean nullable
• is_easy_apply boolean nullable
• is_remote boolean nullable
• is_resume_required boolean nullable
• is_dte_job boolean nullable
• is_advert boolean nullable
• has_few_applies boolean nullable
• has_questions boolean 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 — The entity was not found, or a precondition failed 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.