Store API keys and cash register integrations: self-service setup
Create a store-scoped API key, connect accounting or AI software and prepare a physical cash register integration.
API access and a physical register connector serve different purposes. An API lets another application read selected store data. A register connector must deliver a sale to a specific device and receive confirmation. An API key alone does not print a fiscal receipt.
How do customers create their own API keys?
Owners or managers open API keys and integrations, name the integration and choose stores, resources and expiry. The key is displayed once. Give it to the selected accounting or AI application rather than publishing it in website code.
What data can be filtered?
The read-only API provides products, stock, sales or returns as JSON. A store identifier is mandatory; sales and returns support date and category filters. The server checks key scopes and store assignments. Other customers’ data is inaccessible.
How should you prepare a register connection?
Choose the country, model template and connection method, then confirm VAT code mappings. USB or Serial devices need browser permission initially. Local software and provider APIs need a documented installed adapter. A template assists configuration; it does not certify a working fiscal integration.
When does a receipt number appear in reports?
Only after a confirmed response from the actual register. Unknown outcomes cannot be treated as successful receipts, and retries must not create a second sale. Label printing is separate: dimensions are saved for the computer, and the printer is selected in the browser dialog.
Explore the system in practice.
Discover the system or sign in to your workspace.