Data model

Feedback points

A single extracted point belonging to a feedback_item. Carries the kind (Korrektur/Kritik/Vorschlag/Lob/Frage), the excerpt from the source, and the AI-suggested edit.

Model name: feedback_point
Endpoints: 5
Max page size: 1000

Fields

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

FieldTypeConstraints
kindenum
appliedbool-
excerptstring
max length2000
grant_idstring
max length64ref →grant
applied_atstring
max length32
suggestionstring
max length2000
chapter_keystring
max length64
feedback_item_idstring
max length64

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
kind
applied
excerpt
grant_id
applied_at
suggestion
chapter_key
feedback_item_id

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
feedback_item_iddata__feedback_item_id
chapter_keydata__chapter_key
kinddata__kind
applieddata__applied
statusstatus
is_archivedis_archived
owned_byowned_by

Sort keys

created_atcreated_at
updated_atupdated_at
kinddata__kind

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/feedback_pointfeedback_point: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/feedback_point?limit=20"
GET/xapi2/data/feedback_point/{id}feedback_point: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/feedback_point/OBJECT_ID
POST/xapi2/data/feedback_pointfeedback_point: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/feedback_point \
-d '{"name": "…"}'
PATCH/xapi2/data/feedback_point/{id}feedback_point: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/feedback_point/OBJECT_ID \
-d '{"name": "…"}'
DELETE/xapi2/data/feedback_point/{id}feedback_point: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/feedback_point/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 feedback_point list --limit 5
grantscli feedback_point get <id>
grantscli feedback_point create --grant-id "Hello"
grantscli feedback_point upsert --unique grant_id --csv items.csv
grantscli feedback_point schema # fields & limits

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