Skip to content

Onboarding checklist

Start here

What you exchange with the AIOTIC team, and in which order things have to happen for a smooth go-live.

What you receive from AIOTIC

ItemNotes
Tenant base URLhttps://<tenant>.aiotic.ai. One per company; test and production are separate tenants when both exist.
Sync keyAccepted on /customer/*, /product/*, /customer-product/*. Enough for a standard integration: master data in, orders out through your receive endpoint. Rotatable by a tenant admin.
Integration key (only for headless integrations)Accepted on every endpoint. Issued per project by the AIOTIC team when you build your own review UI or a fully automated flow. Store it as a secret.
App login (tenant admin)To enter the ERP endpoint URL and key in the AIOTIC app's settings screen, or ask your AIOTIC contact to do it.

What you give to AIOTIC

ItemNotes
ERP receive endpoint URLPublic HTTPS, e.g. https://integration.example.com/aiotic/orders.
ERP endpoint keyThe value AIOTIC will send in X-API-KEY on every call to that URL. You generate it (aiotic init does).
Processing webhook URL + key (optional)Only if you want the early, pre-review signal.
Allow-list requirements (optional)If your endpoint is behind an IP allow-list, ask for the tenant's egress addresses.

Sequence

  1. Sandbox first. Build against the mock tenant until the receive endpoint and sync work end to end.
  2. Load master data into the test tenant: customers → products → mappings (Initial load). Run aiotic doctor — all three counts should be > 0.
  3. Connect the receive endpoint (send URL + key to AIOTIC, or enter them in the app as tenant admin). Use Test ERP connection in the app, or ask for a test send.
  4. Process real documents in the test tenant. Watch the ratio of Processed to Attention: a high ATTENTION rate almost always means missing products or customer item mappings, not AI trouble.
  5. Switch on incremental sync (events or reconciliation) so master data stays current without full dumps.
  6. Production tenant: repeat 2–3 with production keys; keep the test tenant for regression.
  7. Operate: monitor /system-status, your endpoint's error rate, and orders stuck in ATTENTION.

Go-live gate

  • [ ] Receive endpoint answers {"success": true, "order_number": …} within a few seconds and is idempotent on request_id
  • [ ] Receive endpoint verifies X-API-KEY in constant time and is only reachable over HTTPS
  • [ ] Business rejections return {"success": false, "error": "<clear text>"} — never a bare HTTP 500 with HTML
  • [ ] Master data complete: every sellable article in /product, every active debtor in /customer
  • [ ] Incremental sync running; no scheduled full re-upload
  • [ ] Keys stored as secrets, not in code or in a browser
  • [ ] Someone owns the ATTENTION queue (in the AIOTIC app or your own tool)

Documentation revision 3 · Published 8 September 2026 · commit 6862d5e. Verified against AIOTIC API v1.0.0. AIOTIC is a product of DevOps Company.