Data model

Applications

Links a candidate to a job. Carries stage (new -> review -> screening -> interview -> offer -> hired | rejected | talent_pool), KI fit-score, source, cover-letter URL, resume URL, and intra-column kanban position.

Model name: application

Endpoints: 5

Max page size: 500

Fields

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

Field	Type	Constraints
tags	`tags`	-
stage	`enum`	enum`new \| review \| screening \| interview \| offer \| hired \| rejected \| talent_pool`
cv_url	`url`	max length`2048`
job_id	`string`	max length`64`ref →`job`
answers	`list`	-
position	`number`	-
fit_flags	`tags`	-
fit_score	`number`	-
source_id	`string`	max length`64`ref →`source`
applied_at	`string`	max length`32`
cv_blob_id	`string`	max length`64`
candidate_id	`string`	max length`64`ref →`candidate`
cover_letter	`string`	max length`16000`
source_label	`string`	max length`200`
fit_reasoning	`string`	max length`4000`
last_stage_at	`string`	max length`32`
rejected_note	`string`	max length`2000`
previous_stage	`string`	max length`32`
fit_computed_at	`string`	max length`32`
rejected_reason	`enum`	enum`not_qualified \| salary_mismatch \| location_mismatch \| culture_mismatch \| withdrew \| ghosted \| filled_internally \| duplicate \| other`

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.

Field	Type	Create	Patch
tags	tags
stage	enum
cv_url	url
job_id	string
answers	list
position	number
fit_flags	tags
fit_score	number
source_id	string
applied_at	string
cv_blob_id	string
candidate_id	string
cover_letter	string
source_label	string
fit_reasoning	string
last_stage_at	string
rejected_note	string
previous_stage	string
fit_computed_at	string
rejected_reason	enum

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

job_iddata__job_id

candidate_iddata__candidate_id

stagedata__stage

source_iddata__source_id

rejected_reasondata__rejected_reason

is_archiveddata__is_archived

status

is_archivedis_archived

owned_byowned_by

created_bycreated_by

Sort keys

created_atcreated_at

updated_atupdated_at

applied_atdata__applied_at

fit_scoredata__fit_score

positiondata__position

last_stage_atdata__last_stage_at

Default: position

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/applicationapplication: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/application?limit=20"

GET/xapi2/data/application/{id}application: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/application/OBJECT_ID

POST/xapi2/data/applicationapplication: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/application \
     -d '{"name": "…"}'

PATCH/xapi2/data/application/{id}application: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/application/OBJECT_ID \
     -d '{"name": "…"}'

DELETE/xapi2/data/application/{id}application: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/application/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 application list --limit 5
atscli application get <id>
atscli application create --job-id "Hello"
atscli application upsert --unique job_id --csv items.csv
atscli application schema   # fields & limits

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