The UI is not the business engine
The browser presents information, collects choices and calls the public API. Authoritative validation, economic rules, state and calculations live behind the API rather than being duplicated in frontend JavaScript.
API-first · headless by design
Use the XIDENA interface. Or build your own.
The XIDENA web application is a client of the same versioned API available to customers. Bring XIDENA economics into the software and workflow your business already uses.
One authoritative contract.
External applications should be able to achieve the same valid business result as the XIDENA web interface without copying XIDENA frontend logic.
HTTPS JSON/api/v1/…company-scopedmachine-readable errorstraceable calculationsidempotent writes
Integration path
Start with files. Move to direct integrations when it makes sense.
CSV and XLSX provide a practical bridge from existing systems. The public API supports customer-built interfaces and integrations as those workflows are exposed and documented.
Inbound
CRM, operations or customer systems can provide People, Offerings, Transactions and other supported data through imports or API integrations.
Processing
XIDENA resolves the applicable configuration and produces the same authoritative economic results used by the XIDENA web application.
Outbound
Export structured results to payroll/payment systems, reporting workflows and other customer systems without rebuilding calculation spreadsheets every period.
Shedina’s developer hint
If the XIDENA UI can validly do it, the public API should be able to do it too. The interface is a reference client, not a private shortcut.