POST /api/adzuna/salaries
Price: 5 credits
Get Adzuna UK labour-market salary stats for a job role (optionally narrowed by location): average advertised salary, comparison to the national average, year-on-year salary and vacancy trends, live vacancy count, top hiring companies, highest-paying areas and in-demand skills.
Fetch UK salary statistics for a job role from Adzuna's Salary Stats Centre. Set what to the role (e.g. accountant, software engineer) and optionally where to a UK location (e.g. london). Returns one item with role, location, average_salary, national_average_salary, salary_vs_national_percent, salary_yoy_percent, vacancy_count, vacancy_yoy_percent, currency, top_companies, fast_facts, top_areas (area, avg_salary, yoy_change, vacancy_count) and skills (name, importance). Location-narrowed queries omit national_average_salary, top_companies and skills.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)what string required — Job role or title to get UK labour-market salary stats for (examples: "accountant", "software engineer", "nurse"; minLength: 1)where string nullable — Optional UK location (city, region or area) to narrow the salary stats (examples: "london", "manchester", "scotland")@type string (default: "AdzunaSalaryStats")role string nullablelocation string nullableurl string nullablecurrency string nullableaverage_salary number nullablenational_average_salary number nullablesalary_vs_national_percent number nullablesalary_yoy_percent number nullablevacancy_count integer nullablevacancy_yoy_percent number nullabletop_companies array (default: [])fast_facts array (default: [])top_areas array (default: [])@type string (default: "AdzunaSalaryArea")area string nullableavg_salary number nullableyoy_change number nullablevacancy_count integer nullableskills array (default: [])@type string (default: "AdzunaSalarySkill")name string nullableimportance number nullable422 — 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 — Role or location not found (no matching salary stats for the given what/where) 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.