/jooble/salaries

POST /api/jooble/salaries

Price: 10 credits

Get Jooble average salary data for a job title and region

How to use it

Get Jooble average salary benchmarks for a job title, optionally scoped to a city, state, or region, across country editions. Returns the average, low and high pay broken down by pay period (hourly, daily, weekly, monthly, yearly) together with the matching country-wide average, how the region compares to the national average, the number of active and recently added jobs, related job titles with their average pay, the top-paying locations for the role (with min/max range and comparison), and the average pay per region.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Job title or role to look up salary data for (minLength: 1)
• region string nullable — City, state, or region to scope the salary figures to
• 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")

Response

• @type string (default: "JoobleSalary")
• region string nullable
• region_id integer nullable
• url string required
• currency string nullable
• default_rate string nullable
• is_reliable boolean nullable
• updated_at string nullable
• active_jobs_count integer nullable
• salary_based_jobs_count integer nullable
• last_week_jobs_count integer nullable
• country_comparison_percent number nullable
• salaries array (default: [])
  • @type string (default: "JoobleSalaryRate")
  • period string required
  • average number nullable
  • low number nullable
  • high number nullable
  • country_average number nullable
• related_queries array (default: [])
  • @type string (default: "JoobleSalaryRef")
  • query string nullable
  • region string nullable
  • url string nullable
  • compared_to_average string nullable
  • salaries array (default: [])
    • @type string (default: "JoobleSalaryRate")
    • period string required
    • average number nullable
    • low number nullable
    • high number nullable
    • country_average number nullable
• top_paying_locations array (default: [])
  • @type string (default: "JoobleSalaryRef")
  • query string nullable
  • region string nullable
  • url string nullable
  • compared_to_average string nullable
  • salaries array (default: [])
    • @type string (default: "JoobleSalaryRate")
    • period string required
    • average number nullable
    • low number nullable
    • high number nullable
    • country_average number nullable
• regions array (default: [])
  • @type string (default: "JoobleSalaryRef")
  • query string nullable
  • region string nullable
  • url string nullable
  • compared_to_average string nullable
  • salaries array (default: [])
    • @type string (default: "JoobleSalaryRate")
    • period string required
    • average number nullable
    • low number nullable
    • high number nullable
    • country_average number 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 — No salary data found for this job title or region 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.