Apply Case Input
Review a suggest input: accept some rows, optionally with an edited value, and reject the rest. Deterministic, no AI call, applied from the stored record.
- An accepted row is written whatever the fill setting says: a human validated it.
- A row whose field changed on the case since the proposal comes back
skippedwithreason: value_changed, so an old proposal never overwrites a newer value. - Idempotent: rows already applied or rejected are returned unchanged. An unknown row id is a 400.
reject_others(defaulttrue) rejects every row you did not list. Passfalseto keep them proposed for a later call.
suggest mode: accept some rows, optionally with an edited value, and reject the rest.Authorizations
API token (starts with pnbx_). Create at https://app.penbox.io/workspace/settings/api. Include as: Authorization: Bearer {token}
Response
The input with its row statuses updated, plus the refreshed case
The case. On the write routes and on the single read it is the full case (same shape as GET /cases/{id}).
Provenance, inferred from your token: api
"api"
What the material is, derived by Penbox from the context and the content
call, note, chat, message, document, other What you sent as context
suggest, auto proposed, partially_applied, applied One paragraph on what the material is about, in the case language
Facts read in the content that no case field can hold. Never written.
The raw material, verbatim. Only returned by GET /cases/{id}/inputs/{input_id}.