Data model

Version snapshots

Versioned point-in-time view of a grant - label, score, summary, and a JSONB snapshot of file contents at that moment. Triggered by manual save, auto-adjust, or external feedback application.

Model name: version_snapshot
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
labelstring
max length32
scorenumber-
summarystring
max length2000
grant_idstring
max length64ref →grant
snapshotdict-
derived_keyslist-
feedback_triggerstring
max length200

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
label
score
summary
grant_id
snapshot
derived_keys
feedback_trigger

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

grant_iddata__grant_id
statusstatus
is_archivedis_archived
owned_byowned_by

Sort keys

created_atcreated_at
updated_atupdated_at
scoredata__score

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/version_snapshotversion_snapshot: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://granttool.de/xapi2/data/version_snapshot?limit=20"
GET/xapi2/data/version_snapshot/{id}version_snapshot: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://granttool.de/xapi2/data/version_snapshot/OBJECT_ID
POST/xapi2/data/version_snapshotversion_snapshot: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://granttool.de/xapi2/data/version_snapshot \
-d '{"name": "…"}'
PATCH/xapi2/data/version_snapshot/{id}version_snapshot: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://granttool.de/xapi2/data/version_snapshot/OBJECT_ID \
-d '{"name": "…"}'
DELETE/xapi2/data/version_snapshot/{id}version_snapshot: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://granttool.de/xapi2/data/version_snapshot/OBJECT_ID

Use in CLI

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

grantscli version_snapshot list --limit 5
grantscli version_snapshot get <id>
grantscli version_snapshot create --grant-id "Hello"
grantscli version_snapshot upsert --unique grant_id --csv items.csv
grantscli version_snapshot schema # fields & limits

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