POS Dealer API
Script the rollout.
The POS Dealer API automates the steps between a signed framework agreement and a producing till. Your system invites operators, creates outlets and runs the rollout plan, the same calls in every market.
The four capability groups
- /posoperators – Invite and manage your operators
- /…/outlets – Create and list outlets per operator
- /…/produce – Execute a rollout plan against entitlements
- /…/templates – Instantiate full CashBoxes from one templateRESULT
Four capability groups carry the whole rollout, agreement to producing CashBox.
- Endpoints across four capability groups
- 8
- Headers on every request
- 3
- Rollout types: queue and outlet
- 2
- Template call creates a full CashBox
- 1
THE API SURFACE
Eight endpoints, four jobs.
Every rollout task maps to one call. The reference carries the full schemas.
| End point | Method | Purpose |
|---|---|---|
| /api/posoperators | POST | Invite a new PosOperator with company data, identifiers and access rights |
| /api/posoperators | GET | List the PosOperators connected to your account |
| /api/posoperators/{id}/outlets | GET | List the outlets of an operator |
| /api/posoperators/{id}/outlets | POST | Create a new outlet for an operator |
| /api/posoperators/{id}/produce | POST | Execute a rollout plan for selected outlets or queues |
| /api/rollout-plans | GET | List available rollout plans with their included products |
| /api/entitlements | GET | List entitlements with total and remaining terms |
| /api/posoperators/{id}/templates | POST | Run a template that creates the CashBox with its Queues and signature creation devices |
THE ROLLOUT FLOW
Agreement to producing till, in four calls.
Each step is one endpoint. Loop the sequence and a hundred outlets roll out the same afternoon.
Invite the operator
Send company data, tax identifiers and contact person. Set access rights: full, read or readwrite.Create the outlets
Register each location with outlet number, address and contact.Execute the rollout plan
Produce products against your entitlements for the selected outlets or queues.Run the template
One call instantiates the CashBox with its Queues and signature creation devices.
Entitlements come first: purchase them up-front, for example through a framework agreement, then draw them down per rollout. GET /api/entitlements shows total and remaining terms, so your system tracks stock before every batch.
TEMPLATES
One template. A complete CashBox.
The template schema defines the full configuration: the CashBox, its Queues and the signature creation devices. Market-specific initialisation blocks configure each country inside the same structure.
"ftCashBoxId": "guid",
"ftSignaturCreationDevices": [ ... ],
"ftQueues": [{
"configuration": {
"init_ftQueueAT": [ ... ],
"init_ftQueueDE": [ ... ],
"init_ftQueueFR": [ ... ],
"init_ftQueueIT": [ ... ]
}
}]- Repeatable
- The same template rolls out identical, pre-approved configurations across every outlet. No hand-built CashBoxes, no drift.
- Per market
- Initialisation blocks per country configure Queue and signature creation unit in one structure.
- Scriptable
- Your provisioning system calls the endpoint per outlet. On-site time per outlet drops from hours to minutes.
One outlet or a hundred. The script is the same.
ACCESS
Three headers, clear permissions.
Every request carries the same three headers. Operator access rights (full, read or readwrite) limit what each connection touches.
accountid
Identifies your dealer account.accesstoken
Authenticates the request.market
Selects the target market for the call.
SELF-SERVE
Everything you need before a call.
Judge feasibility and fit on your own terms. The stack is documented, public and testable today.
Documentation
Read the docsFull API reference, integration guides and error semantics in English at docs.fiskaltrust.eu.
GitHub
Browse the reposThe Middleware source, launcher, devkit and demo implementations, in the open.
Sandbox
Get accessA near-full copy of the live system. Sign test receipts without legal obligation.
Academy
See the programStructured onboarding for your team, from first request to certified rollout.
FAQ
Before you script the rollout.
Short answers, the reference carries the schemas.
Who is this API for?
POS dealers and platforms managing many operators and outlets. Your back-office or provisioning system calls the API instead of a technician clicking through the Portal.
Where do entitlements come from?
Purchase entitlements up-front, for example through a framework agreement, then draw them down per rollout. The entitlements endpoint shows total and remaining terms.
What does a rollout plan contain?
An identifier, a rollout type of queue or outlet, and the included products. Execute a plan against selected outlet or queue identifiers.
What does a template create?
A configured CashBox with its Queues and signature creation devices, including market-specific initialisation. One call per outlet.
What do operator access rights control?
Each invited PosOperator carries an access level: full, read or readwrite. Set the level at the invitation.
Where do the credentials come from?
Your dealer account in the fiskaltrust.Portal issues the accountid and accesstoken. Send both with the market header on every request. The API also lists a PosOperator's Queues and returns order details per order number; the reference has the exact paths.
Script your next rollout.
Read the reference, wire the four calls into your provisioning system and roll out the next hundred outlets from your desk.
You talk to real people