/personio/jobs

POST /api/personio/jobs

Price: 5 credits

Get one job posting from a company's Personio career board by board handle and posting id: the job title, legal entity, office and additional offices, department, employment type, seniority, schedule, years of experience, occupation, keywords, salary range where the company published one, and the full posting text split into its named sections.

How to use it

Get one Personio job posting. Identity is (tenant, job): the same numeric id is reused across companies, so a posting id alone does not identify a job and a foreign id under this handle is a 412. job also accepts a full posting URL, which fills tenant in for you. Leave language empty unless the caller asked for a specific one; setting it restricts the text to that language and returns an empty description, not an error, when the posting was not written in it. Use personio/jobs/search when you have the company but not the id.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• tenant string required — Company board handle from its Personio career board URL ({tenant}.jobs.personio.de). Accepts a bare handle or a full board URL (examples: "chrono24", "tonies"; minLength: 1)
• job integer required — Job posting id. Accepts the bare numeric id, or a full posting URL ({tenant}.jobs.personio.de/job/{id}), which fills tenant in for you (examples: 2717899; >: 0)
• language string — Two-letter language code to read the posting text in. Leave empty to get the text in whichever language the company wrote it in (default: ""; examples: "en", "de"; maxLength: 5)

Response

• @type string (default: "PersonioJob")
• id integer required
• url string nullable
• tenant string nullable
• subcompany string nullable
• office string nullable
• additional_offices array (default: [])
• department string nullable
• recruiting_category string nullable
• employment_type string nullable
• seniority string nullable
• schedule string nullable
• years_of_experience string nullable
• occupation string nullable
• occupation_category string nullable
• keywords array (default: [])
• created_at string nullable
• description string nullable
• sections array (default: [])
  • @type string (default: "PersonioJobSection")
  • name string nullable
  • content string nullable
• salary object nullable
  • @type string (default: "PersonioSalary")
  • min number nullable
  • max number nullable
  • currency_code string nullable
  • currency_symbol string nullable
  • interval 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 such posting on this Personio board, or no board exists for this handle 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.