/infojobs/salaries

POST /api/infojobs/salaries

Price: 1 credit

Get InfoJobs salary benchmark for a job title in a Spanish province

How to use it

Get InfoJobs (Spain) salary statistics for a job title, optionally scoped to a Spanish province. Returns the gross-annual pay range — low, average and high — in euros, the number of declared salaries the estimate is based on, the salary distribution histogram, and the latest related job offers for the role and province. Omit the province for the default (Madrid) view.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• puesto string required — Job title (puesto) to look up Spanish salary data for (examples: "enfermero/a", "desarrollador de software"; minLength: 1)
• provincia string nullable — Spanish province to scope the salary to; omit for the default (Madrid) view (examples: "Madrid", "Barcelona", "Valencia/València")

Response

• @type string (default: "InfojobsSalary")
• province string nullable
• url string required
• currency string (default: "EUR")
• period string nullable
• low number nullable
• average number nullable
• high number nullable
• sample_count integer nullable
• distribution array (default: [])
• related_offers array (default: [])
  • @type string (default: "InfojobsSalaryOffer")
  • url string nullable
  • company string nullable
  • image string nullable
  • location string nullable
  • posted string nullable
  • contract_type string nullable
  • workday string nullable
  • salary 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 — No salary data found for this job title and province 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.