Appearance
Headless limits today
Driving orders via the API
This page is deliberately blunt. If you plan to integrate without the AIOTIC app (models B and C), these are the things the public API does not offer yet, and what to do instead. Proposed additions are in the appendix; nothing there exists until the changelog says so.
| Capability | Status | Workaround today |
|---|---|---|
| Submit corrections to an extracted order before sending | Not available. Corrections are made in the AIOTIC app; POST /erp/send merges them. | Apply corrections on your side: your receive endpoint gets the AI's reading plus app corrections; adjust in your ERP after booking (match on request_id), or route the order to the app for the fix. |
| Cancel an order | Not available (CANCELED is set from the app). | Leave it unsent; track it as ignored in your system. Ask an operator to cancel in the app if the queue must stay clean. |
| Status-change notifications (webhook per transition) | Not available. | Order watcher polling the list; the processing webhook for the single "landed" moment. |
| Signed / retried webhooks | Processing webhook is static-key, best effort. | Verify the key; treat as a hint; reconcile by polling. |
| Batch upserts for master data | One request per record. | Parallel upserts (4–8) via the SDK engine; only changed records. |
updated_since / ETag on list endpoints | Not available. | Keep your own state (fingerprints for master data, last status for orders). |
Filtering order_status/list by status or date | Not available; newest-first pagination only. | Watcher over the first pages; nightly full page walk for reporting. |
| Scoped / read-only keys | Two keys: integration (all) and sync (master data). | Keep the integration key in one service; give everything else the sync key or no key. |
| Reprocess with instructions ("ignore page 2") | App only. | Use the app for that order. |
| Per-order customer hint on upload | Not available; identification is evidence-based. | Ensure the customer record has VAT/e-mail/address; add item mappings. |
What is fully available headless
Upload (files and raw e-mails, incl. split), classify, status, list, group view, per-file download, retry, rejected-mail triage and override, ERP send with correct locking and rollback, complete master-data CRUD and search, health and platform status.
That is enough for model C (automated send of clean orders, humans for the rest) and for a read-only model B (your UI shows and sends, corrections happen in the app or in your ERP).
If you need more
Tell your AIOTIC contact which item above blocks you. The proposal appendix exists so we can prioritise with real integrator needs.