Dashboard or API — choosing your path
Every capability exists in both the web dashboard and the REST API. Most teams use both: the dashboard to explore and operate, the API to automate.
The dashboard
The dashboard is the no-code way to use TaxLens. It's the right starting point for everyone, and the home base for finance and operations teams. From it you can:
- calculate tax for any stay and inspect the full breakdown;
- register properties and let TaxLens map them to jurisdictions;
- save bookings, issue invoices and credit notes, and process refunds;
- pull tax-liability reports and export them for filing;
- manage your team, legal entities, and API keys.
The Dashboard guide walks through every screen.
The API
The API is how you wire TaxLens into your own systems — a booking engine that needs tax at checkout, a PMS that issues invoices automatically, a back office that syncs liability into your accounting stack. It exposes the same engine and the same e-invoicing system of record the dashboard uses.
The API integration guide covers authentication, the calculate and booking endpoints, e-invoicing, and reporting — with runnable examples. For the exhaustive endpoint-by-endpoint schema, use the API Reference page in the left app navigation.
Which should I use?
- Just exploring or operating manually? Use the dashboard.
- Calculating tax inside your own product? Use the API's calculate endpoint.
- Issuing invoices at volume? Drive bookings + issuance through the API, and use the dashboard to inspect, correct, and report.
The two share one source of truth. A booking created via the API appears in the dashboard; an invoice issued in the dashboard is retrievable via the API. Pick whichever fits each task.