> ## Documentation Index
> Fetch the complete documentation index at: https://docs.maesn.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Tripletex
> Integrate Tripletex easily with Maesn's Unified API. See the documentation with detailed system coverage and setup prerequisites.
**TARGET\_SYSTEM:** `tripletex`
| | Read | Create | Update | Delete | Webhook |
| -------------------- | :----------------------------------------------------: | :----------------------------------------------------: | :----------------------------------------------------: | :----------------------------------------------------: | :----------------------------------------------------: |
| Accounts | | | | | |
| Async task | | | | | |
| Bank accounts | | | | | |
| Bills | | | | | |
| Bill lines | | | | | |
| Booking proposals | | | | | |
| Contacts | | | | | |
| Customers | | | | | |
| Credit notes | | | | | |
| Dimensions | | | | | |
| Expenses | | | | | |
| Files | | | | | |
| Fiscal years | | | | | |
| Goods receipts | | | | | |
| Goods receipt lines | | | | | |
| Invoices | | | | | |
| Invoice lines | | | | | |
| Items | | | | | |
| Journals | | | | | |
| Journal entries | | | | | |
| Offers | | | | | |
| Offer lines | | | | | |
| Open items | | | | | |
| Payments | | | | | |
| Payment terms | | | | | |
| Projects | | | | | |
| Purchase orders | | | | | |
| Purchase order lines | | | | | |
| Sales orders | | | | | |
| Sales order lines | | | | | |
| Suppliers | | | | | |
| Tax rates | | | | | |
| Transactions | | | | | |
| Trial balance | | | | | |
| Units | | | | | |
| Users | | | | | |
| Vendor credits | | | | | |
= Supported by Maesn
= Not yet supported
## How to Connect to Tripletex
Tripletex uses token-based authentication. Two tokens are combined into a session token: a `consumer token` that identifies your integration (configured once on your maesn tenant), and an `employee token` that identifies the Tripletex account, which the end user enters when connecting.
You need an active Tripletex account. Creating API tokens requires administrator access.
Obtain the `consumer token` for the integration in Tripletex. The consumer token identifies the integration (not an individual user) and is the same for all of your end users.
See Tripletex's [authentication and tokens documentation](https://developer.tripletex.no/docs/documentation/authentication-and-tokens/) for how consumer tokens are issued.
In Tripletex, an administrator creates an `employee token` under "user settings" > "API access". This token identifies the account whose data you want to access, and is the value each end user enters when connecting.
Before connecting, share your `consumer token` with your contact person at maesn so we can configure it on your API tenant. This is a one-time setup.
If you are not sure who your technical contact is, do not hesitate to [reach out to us](https://www.maesn.com/contact).
Once it is configured, connect through maesn Connect — or the [create account](https://docs.maesn.com/api-reference/auth/create-account) endpoint — by entering your `employee token`.
## Sandbox environment
**TARGET\_SYSTEM:** `tripletex-sandbox`
Tripletex provides a separate test environment. To connect against it, use the sandbox target system identifier:
The sandbox behaves exactly like production but points at Tripletex's test environment (`https://api-test.tripletex.tech`) and requires its own consumer and employee tokens.
## Multi-company (accountant) access
A regular employee token accesses a single company, and no company selection is required. An `accountant` (company-owned) token can access several client companies. For those tokens, the list of accessible companies is available through the [Get companies](/api-reference/auth/get-companies) endpoint, and the desired company can be selected during the connection flow.