Inbox items
Stamp incoming documents in the inbox to turn them into supplier invoices or transactions.
Endpoints
POST/api/v1/companies/:companyId/inbox-items/:id/stamp: Mark an inbox item as consumed by a journal entry.
POST /api/v1/companies/:companyId/inbox-items/:id/stamp
inbox-items.stamp · scope documents:write
Mark an inbox item as consumed by a journal entry.
Sets created_journal_entry_id on an invoice_inbox_items row so the item drops out of the active inbox todo list. Use when the document was linked to a JE via a separate call and you need to close the inbox item independently.
Use when: An inbox document has already been attached to a verifikation (via documents link) but the inbox item itself was not stamped at link time: e.g. when using the v1 link endpoint without inbox_item_id.
Don't use for: Creating a new journal entry from an inbox item: use the invoice-inbox extension book-direct route for that.
Pitfalls
- Idempotency-Key is mandatory.
- The inbox item and journal_entry_id must both belong to the caller's company.
- Stamping with a different journal_entry_id than the one already set returns CONFLICT: the item is already resolved.
Risk: low · Idempotent: yes · Reversible: no · Dry-run supported: no
Example request
{
"journal_entry_id": "dcccb3c5-b44a-4536-82fa-f0b9bb77f900"
}
Example response
{
"data": {
"id": "4d2fcdbb-13b3-4ff3-911f-a4cc82f1f6db",
"created_journal_entry_id": "dcccb3c5-b44a-4536-82fa-f0b9bb77f900"
},
"meta": {
"request_id": "req_…",
"api_version": "2026-05-12"
}
}