Data model

Jobs

An open role. Carries title, department, location, employment type, KI fit-profile (requirements + knockout criteria), status, and a public careers-page slug. Parent for applications.

Model name: job
Endpoints: 5
Max page size: 200

Fields

Per-field validation rules. Values that violate any constraint are rejected with 400 before they reach the database.

FieldTypeConstraints
slugstring
tagstags-
colorstring
max length24
titlestring
max length200
publicbool-
remoteenum
enumonsite | hybrid | remote
statusenum
enumdraft | open | paused | closed | filled
countrystring
max length80
summarystring
max length600
benefitsstring
max length4000
currencystring
max length8
languagestring
max length16
locationstring
max length120
team_idslist-
closed_atstring
max length32
headcountnumber-
opened_atstring
max length32
seniorityenum
enumjunior | mid | senior | lead | principal
departmentstring
max length120
salary_maxnumber-
salary_minnumber-
descriptionstring
max length16000
nice_to_havestring
max length4000
requirementsstring
max length8000
employment_typeenum
enumfull_time | part_time | internship | working_student | freelance | contract
ai_screen_promptstring
max length4000
responsibilitiesstring
max length8000
ai_screen_enabledbool-
hiring_manager_idstring
max length64
salary_visibilityenum
enumpublic | team | private
target_close_datestring
max length32
external_apply_urlurl
max length2048
knockout_questionslist-
screening_questionslist-

Mutability

Which fields can you send, and when? Anything without a marker is server-managed - sending it isn't an error, it's silently ignored.

Create-only - read from POST body.Patchable - read from PATCH body.Server-managed - ignored on the body.
FieldCreatePatch
slug
tags
color
title
public
remote
status
country
summary
benefits
currency
language
location
team_ids
closed_at
headcount
opened_at
seniority
department
salary_max
salary_min
description
nice_to_have
requirements
employment_type
ai_screen_prompt
responsibilities
ai_screen_enabled
hiring_manager_id
salary_visibility
target_close_date
external_apply_url
knockout_questions
screening_questions

Fields marked create-only but not patchable are immutable after creation. Server-managed fields include id, timestamps, ownership, and status.

Filtering & sorting

Combinable on list endpoints. Repeating a filter key produces an IN clause; prefixing a sort key with - reverses direction. Example: ?status=open&status=blocked&sort=-created_at.

Filter keys

titledata__title
departmentdata__department
locationdata__location
employment_typedata__employment_type
senioritydata__seniority
remotedata__remote
status
publicdata__public
hiring_manager_iddata__hiring_manager_id
tagsdata__tags
statusstatus
is_archivedis_archived
owned_byowned_by
created_bycreated_by

Sort keys

created_atcreated_at
updated_atupdated_at
titledata__title
opened_atdata__opened_at
target_close_datedata__target_close_date

Default: created_at

Endpoints

Each endpoint below lists its HTTP method, path, and the PAT scope it needs. Code samples cover curl, JavaScript, TypeScript, Python, Rust, Java, and WebSocket.

GET/xapi2/data/jobjob:list

List objects

Returns a paginated list of objects you can read. Default page size is 20; pass ?limit= to change (capped per type). Use ?after=<id> for keyset pagination on created_at-sorted lists, or ?offset= for offset paging.

curl -H "Authorization: Bearer pat_…" \
"https://www.ki-bewerber-management.de/xapi2/data/job?limit=20"
GET/xapi2/data/job/{id}job:read

Read one

Returns the object by id. 404 if it does not exist or you cannot read it (the two cases are intentionally conflated).

curl -H "Authorization: Bearer pat_…" \
https://www.ki-bewerber-management.de/xapi2/data/job/OBJECT_ID
POST/xapi2/data/jobjob:create

Create

Creates a new object. Body is a flat JSON dict of field values. Server-side fields (id, timestamps, ownership) are filled automatically; only fields listed below as creatable are read from the body.

curl -H "Authorization: Bearer pat_…" \
-H "Content-Type: application/json" \
-X POST https://www.ki-bewerber-management.de/xapi2/data/job \
-d '{"name": "…"}'
PATCH/xapi2/data/job/{id}job:update

Update

Partial update. Only fields included in the body are touched; everything else is preserved. Same allow-list as create, minus the fields that are immutable post-create.

curl -H "Authorization: Bearer pat_…" \
-H "Content-Type: application/json" \
-X PATCH https://www.ki-bewerber-management.de/xapi2/data/job/OBJECT_ID \
-d '{"name": "…"}'
DELETE/xapi2/data/job/{id}job:delete

Delete

Removes the object. It vanishes from every default list immediately and stops being returned by read / list.

curl -H "Authorization: Bearer pat_…" \
-X DELETE https://www.ki-bewerber-management.de/xapi2/data/job/OBJECT_ID

Use in CLI

The same endpoints are also exposed via the KI BMS CLI. For scripts, CI, and bulk imports it's usually the faster path.

atscli job list --limit 5
atscli job get <id>
atscli job create --title "Hello"
atscli job upsert --unique title --csv items.csv
atscli job schema # fields & limits

Full command reference, profiles, CSV import, auto-retry, NDJSON streaming → /docs/cli