Connecting Lexware Office (formerly lexoffice)
lexoffice is now called Lexware Office. The Public API is available from the XL version. It works with an API key, allows 2 requests per second and reports changes by webhook. Invoices, contacts, articles and receipts can be created and read. A custom integration pays off when no ready-made connector covers your workflow.
What Lexware Office is and who uses it
Lexware Office is accounting and invoicing software in the browser. Companies write quotes and invoices in it, capture receipts and keep their books. The former name lexoffice still appears often in search queries, forums and older guides. It is the same product. According to the documentation, existing integrations with the old gateway api.lexoffice.io should be switched to the new address. If you run an older integration, you should check this.
Which interfaces Lexware Office offers
| Component | What applies according to the Lexware documentation |
|---|---|
| Access | Public API from Lexware Office version XL. New address api.lexware.io since 26 May 2025; the old lexoffice gateway was announced to run until December 2025. |
| Authentication | API key as a bearer token in the Authorization header, created in the Public API management of Lexware Office |
| Rate limit | Up to 2 requests per second; above that the API responds with HTTP 429 |
| Data objects | Invoices, credit notes, delivery notes, quotes, order confirmations, incoming receipts, contacts, articles, files; payment status of documents (read-only) |
| Webhooks | Event subscriptions, for example for new or changed invoices, contacts and articles. The message contains the event and the ID, signed with RSA-SHA512 in the header X-Lxo-Signature. |
| E-invoicing | Invoices and credit notes with the profiles ZUGFeRD (EN 16931) and XRechnung, including the Leitweg-ID for public authorities |
The limit of 2 requests per second is no problem day to day, but it is for the first import: thousands of contacts or articles need a queue. Webhooks deliver only the ID, and the integration then fetches the data through the API. That counts toward the limit as well.
Typical connections and data objects
- Customer is created as a contact as needed
- Order or deal becomes an invoice on receipt
- Refund becomes a credit note on receipt
- Payment status is reported back to the source by webhook
Common sources are shops and CRM systems, such as Shopify with Lexware Office, Shopware with Lexware Office or HubSpot with Lexware Office. Ready-made integrations exist as well, for example from the trades software HERO.
Where standard connectors reach their limits
Plan
Without version XL there is no Public API. Check this before any planning.
Bulk data
At 2 requests per second, large imports take time. Without a queue and retries, a run breaks off.
Payments
The API provides the payment status of documents read-only. Reconciliation with payment providers needs its own logic.
Special cases
Partial invoices, advance payments or deviating tax rates are not covered by many connectors.
How we connect Lexware Office
You create an API key with the required rights in Lexware Office, and we store it encrypted on our server in Germany. All requests go through a queue that respects the limit and waits on HTTP 429. We verify webhooks using the signature. For e-invoices we use the profiles of the API, see e-invoice integration.
Frequently asked questions
Is lexoffice the same as Lexware Office?
Yes. lexoffice is now called Lexware Office. The API was renamed as well and runs at api.lexware.io.
Which version do I need for the API?
According to Lexware, the Public API is available from version XL.
Can Lexware Office create e-invoices through the API?
Yes. Invoices and credit notes can be created with the profiles ZUGFeRD or XRechnung. According to the documentation, the PDF preview of an XRechnung is not a valid e-invoice; the XML file is what counts.
What does a Lexware Office integration cost?
A simple connection between two systems starts at €1,900 net, operation from €149 per month.
Sources
- Lexware API Documentation (gateway, authentication, rate limit, endpoints, event subscriptions, e-invoicing), retrieved on 20 Oct 2026
- Lexware: Public API of Lexware Office (available from version XL), retrieved on 20 Oct 2026
- Lexware Partner: HERO, retrieved on 20 Oct 2026
Connections with Lexware Office
HubSpot → Lexware Office
Won HubSpot deals become invoices in Lexware Office (formerly lexoffice): what apps can do, where the return path is missing and what custom code looks like.
Pipedrive → Lexware Office
Quote, order confirmation and invoice from Pipedrive deals in Lexware Office (formerly lexoffice): what the partner app does and when custom code helps.
Shopify → Lexware Office
Shopify orders as invoices in Lexware Office (formerly lexoffice): what the app does, where payments and e-invoicing fall short, what custom code looks like.
Shopware → Lexware Office
Shopware invoices as vouchers in Lexware Office (formerly lexoffice): which plugins exist, where backfills and sales channels fall short, how we build it.
Related
Shopify → Lexware Office
Shopify orders as invoices in Lexware Office (formerly lexoffice): what the app does, where payments and e-invoicing fall short, what custom code looks like.
HubSpot → Lexware Office
Won HubSpot deals become invoices in Lexware Office (formerly lexoffice): what apps can do, where the return path is missing and what custom code looks like.
Add e-invoicing
Generate XRechnung and ZUGFeRD from your existing software and process incoming e-invoices automatically.
