> ## 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.
# Lexware Office
> Integrate Lexware Office easily with Maesn’s Unified API. See the documentation with detailed system coverage and setup prerequisites.
**TARGET\_SYSTEM:** `lexware-office`
| | 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
= On demand - contact us
= Not supported by Lexware Office
## How to connect to Lexware Office
As a customer of Lexware Office, you can easily retrieve the API key used for connecting to your Lexware Office accounting data.
Before you begin, make sure you have the following:
* A Lexware Office account with administrator permissions to create and retrieve the API key.
Navigate to the [add-ons page](https://app.lexware.de/addons/public-api).
Log in to Lexware Office using your account credentials and [retrieve the API key](https://developers.lexware.io/docs/#lexware-api-documentation-introduction).
Paste your Lexware Office API key in to the 'API key' field in maesn Connect and press 'submit'. If the API key is valid, the connection will be established and a success message will be displayed.
Your Lexware account is now connected!
## Webhooks
Lexware Office supports the following parameters for webhooks:
Resources:
* `CUSTOMER`
* `SUPPLIER`
* `ITEM`
* `INVOICE`
* `PAYMENT`
* `TOKEN`
Event types:
* `CREATED`
* `UPDATED`
* `DELETED`
* `REVOKED`
There is a special webhook resource called `token` that is triggered when a user's Lexware Office token is revoked. This can happen if the user revokes access in their Lexware Office account settings or if the token expires and cannot be refreshed.
Lexware Office needs both resource and event type to be able to send webhook events. The subscription is created **per customer**, which means for each customer, you will create a customized subscription for the events and resources you want to be notified about.
To set this up, call Maesn's create webhook endpoint `POST /webhooks` with the following example body:
```javascript Example code snippet theme={null}
const response = await axios.post(url, {
"callbackUrl": callbackUrl,
"eventType": "CREATED",
"resource": "CUSTOMER"
}, {
headers: {
'X-API-KEY': apiKey,
'X-ACCOUNT-KEY': accountKey
}
});
```
It will return the `id` associated with the subscription:
```json Example response theme={null}
{
"data": {
"id": "550e8400-e29b-41d4-a716-446655440000",
"callbackUrl": "https://example.com/webhook-endpoint/12345",
"createdDate": "2026-01-22T16:44:37.252Z",
"expiresDate": "null",
"secret": "2f1fd5f883d4c0adf5b31b91e4d6ae2d2975620c67bac8fdb864c78047b1d522"
"updatedDate": "2026-01-22T16:44:37.252Z"
},
"meta": {}
}
```
At this point, your system is ready to receive end-user–related events at the callback URL you provided. The event response will provide the following information:
```json Example event body theme={null}
{
"eventType": "CREATED",
"filterDate": null, //not supported by lexware
"resource": "CUSTOMER",
"resourceId": "1605408d-ed88-4228-8a12-ab857a2972d8",
"userId": null //not supported by lexware
}
```
To delete the webhook subscription, you can call the `DELETE` `/webhooks/{webhookId}` endpoint provinding both your `X-API-KEY` and the end user `X-ACCOUNT-KEY`.