Integration · UAE and Jordan
Any till and Otto
Your point of sale posts receipts to Otto over an API key, or you drop the daily file in and Otto works out its shape.
Working today
OttoHow it works
- Create an API key in Settings, API keys. It is shown once.
- Your till, or your integrator, posts up to 500 receipts a call to /api/pos/receipts.
- Or export the daily sales file and drop it on Import sales.
- Answer Otto's one question about any column it cannot place. The next file imports silently.
Every way in
Working today
- Direction
- Till to Otto
- Cadence
- Nightly, or as each receipt is posted
- Format
- JSON over HTTPS, or CSV and XLSX
- Duplicates
- By source reference; a re-post is ignored
Before
The nightly report is emailed to an inbox and typed into a spreadsheet at month end.
After
Every receipt is a posted sale by the morning, with tax split out and the branch tagged.
Our till is on-premise with no API.
The daily file path works for any till that can export a report. Otto reads the header row wherever it sits.
What if a receipt is posted twice?
The second post carries the same source reference and is ignored. The response tells you which receipts were recorded.
Can our integrator do this without us?
Yes. The API guide is written for them, and the key is scoped to receipts only.