All integrations

Lexware Office

BUSINESS · COMMERCE & FINANCE

Contacts, invoices, quotations, and vouchers in the account they connected.

Connecting Lexware Office in practice

Lexware Office allows a client just 2 requests per second, which makes it one of the slowest accounting APIs to sync against, and every resource carries a `version` field for optimistic locking so a write that sends a stale version is rejected rather than merged. The credential is also minted by the account holder in the app rather than issued to your integration, and the product was renamed from lexoffice, so the old developer domain now redirects.

Scopes that draw scrutiny

  • API key / access token The documentation uses the two terms interchangeably for one credential, passed as `Authorization: Bearer {accessToken}`. It is generated by a user at app.lexware.de/addons/public-api, so its reach is that user’s account.

Rate limits

  • "A client can make up to 2 requests per second to the Lexware API."
  • Documented list responses page at 25 items ("size": 25).

Worth knowing

  • Every resource has a `version` that increments on each change, and writes use it for optimistic locking — so a read-modify-write agent must carry the version through or lose the update.
  • The API key is created by the customer, not by you: onboarding is "ask the account owner to generate a key in the add-ons area", which means no OAuth consent screen and no way to request narrower access.
  • developers.lexoffice.io now resolves to developers.lexware.io, so older bookmarks, sample code and any hardcoded documentation links need rewriting after the rename.
  • At 2 requests per second a full ledger backfill is measured in hours, so bulk work has to be scheduled rather than run on demand.

Checked against Lexware Public API docs (2026-09-29)

Acts as the person, not as itself

Each user connects their own account. Every call carries both identities — the agent and the person it is acting for — so the agent can never reach past what that individual can already do.

Credentials never touch the agent

Tokens live in the vault and attach server-side at call time. The agent holds a session, not a secret, and revoking access does not mean rotating a key.

Every call on the record

Who asked, which agent acted, which action ran, and the verdict that let it through — one audit trail across every integration, not one per vendor.

What an agent can do

Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.

lexoffice_delete_v1_articles_by_idWRITE

Deletes the article with id value {id}. Returns 204 on success, or 404 if the id does not exist. via DELETE /v1/articles/{id}

articles.write
lexoffice_delete_v1_event_subscriptions_by_subscriptionidWRITE

Deletes an event subscription with the id {subscriptionId}. On success, you will receive a status code 204 (No Content). via DELETE /v1/event-subscriptions/{subscriptionId}

no provider scope
lexoffice_get_v1_articlesREAD

Returns the articles that fulfill the criteria given by filters filter_1 to filter_n using a paging mechanism. If more than one filter is given, the logical connector is AND. Filters that are not set are ignored. To check the maximum page size for this endpoint, see Paging of Resources. via GET /v1/articles

articles.read
lexoffice_get_v1_articles_by_idREAD

Returns the article with id value {id}. via GET /v1/articles/{id}

articles.read
lexoffice_get_v1_contactsREAD

Returns the contacts that fulfill the criteria given by filters filter_1 to filter_n using a paging mechanism. If more than one filter is given, the logical connector is AND. Filters that are not set are ignored. To check the maximum page size for this endpoint, see Paging of Resources. via GET /v1/contacts

contacts.read
lexoffice_get_v1_contacts_by_idREAD

Returns the contact with id value {id}. via GET /v1/contacts/{id}

contacts.read
lexoffice_get_v1_countriesREAD

Retrieve list of currently known countries. via GET /v1/countries

no provider scope
lexoffice_get_v1_credit_notes_by_idREAD

Returns the credit note with id value {id}. via GET /v1/credit-notes/{id}

credit-notes.read
lexoffice_get_v1_credit_notes_by_id_documentREAD

To download the PDF file of a credit note document, you need its documentFileId. This id is usually returned by the credit note resource. However, PDF document file rendering must be triggered separately via this endpoint for credit notes created through the API with the status open. via GET /v1/credit-notes/{id}/document

credit-notes.read
lexoffice_get_v1_delivery_notes_by_idREAD

Returns the delivery note with id value {id}. via GET /v1/delivery-notes/{id}

delivery-notes.read
lexoffice_get_v1_delivery_notes_by_id_documentREAD

To download the PDF file of a delivery note document, you need its documentFileId. This id is usually returned by the delivery note resource. However, PDF document file rendering must be triggered separately via this endpoint for delivery notes created through the API with the status open. via GET /v1/delivery-notes/{id}/document

delivery-notes.read
lexoffice_get_v1_down_payment_invoices_by_idREAD

Returns the down payment invoice with id value {id}. via GET /v1/down-payment-invoices/{id}

invoices.read
lexoffice_get_v1_dunnings_by_idREAD

Returns the dunning with id value {id}. via GET /v1/dunnings/{id}

dunnings.read
lexoffice_get_v1_dunnings_by_id_documentREAD

To download the PDF file of a dunning document, you need its documentFileId. This id is usually returned by the dunning resource. However, PDF document file rendering must be triggered separately via this endpoint for dunnings created through the API. via GET /v1/dunnings/{id}/document

dunnings.read
lexoffice_get_v1_event_subscriptionsREAD

Returns all your event subscriptions. via GET /v1/event-subscriptions

no provider scope
lexoffice_get_v1_event_subscriptions_by_subscriptionidREAD

Returns the event subscription with the id {subscriptionId}. via GET /v1/event-subscriptions/{subscriptionId}

no provider scope
lexoffice_get_v1_invoices_by_idREAD

Returns the invoice with id value {id}. via GET /v1/invoices/{id}

invoices.read
lexoffice_get_v1_invoices_by_id_documentREAD

To download the PDF file of an invoice document, you need its documentFileId. This id is usually returned by the invoice resource. However, PDF document file rendering must be triggered separately via this endpoint for invoices created through the API with the status open. via GET /v1/invoices/{id}/document

invoices.read
lexoffice_get_v1_order_confirmations_by_idREAD

Returns the order confirmation with id value {id}. via GET /v1/order-confirmations/{id}

order-confirmations.read
lexoffice_get_v1_order_confirmations_by_id_documentREAD

To download the PDF file of an order confirmation document, you need its documentFileId. This id is usually returned by the order confirmation resource. However, PDF document file rendering must be triggered separately via this endpoint for order confirmations created through the API with the status open. via GET /v1/order-confirmations/{id}/document

order-confirmations.read
lexoffice_get_v1_payment_conditionsREAD

Retrieve list of currently configured payment conditions. via GET /v1/payment-conditions

no provider scope
lexoffice_get_v1_payments_by_voucheridREAD

Retrieve payment information of a voucher. via GET /v1/payments/{voucherId}

payments.read
lexoffice_get_v1_posting_categoriesREAD

Retrieve list of currently known posting categories. via GET /v1/posting-categories

no provider scope
lexoffice_get_v1_print_layoutsREAD

Retrieve the list of print layouts. Lexware accepts ANY sales-voucher read scope for this call; the connection is checked for invoices.read here. via GET /v1/print-layouts

invoices.read
lexoffice_get_v1_profileREAD

Retrieve your basic profile information. via GET /v1/profile

profile.read
lexoffice_get_v1_quotations_by_idREAD

Returns the quotation with id value {id}. via GET /v1/quotations/{id}

quotations.read
lexoffice_get_v1_quotations_by_id_documentREAD

To download the PDF file of a quotation document, you need its documentFileId. This id is usually returned by the quotation resource. However, PDF document file rendering must be triggered separately via this endpoint for quotations created through the API with the status open. via GET /v1/quotations/{id}/document

quotations.read
lexoffice_get_v1_recurring_templatesREAD

Retrieve a collection of recurring templates. The result returns only part of the most relevant data which are the referenced contact (only id and name), total price, payment conditions and the complete recurring templates settings. The naming of objects and properties are the same, though. via GET /v1/recurring-templates

recurring-templates.read
lexoffice_get_v1_recurring_templates_by_idREAD

Returns the recurring template with id value {id}. via GET /v1/recurring-templates/{id}

recurring-templates.read
lexoffice_get_v1_voucherlistREAD

To check the maximum page size for this endpoint, see Paging of Resources. via GET /v1/voucherlist

voucherlist.read
lexoffice_get_v1_vouchers_by_idREAD

Returns the voucher with id value {id}. via GET /v1/vouchers/{id}

vouchers.read
lexoffice_post_v1_articlesWRITE

The contents of the article are expected in the request’s body as an application/json. via POST /v1/articles

articles.write
lexoffice_post_v1_contactsWRITE

The contents of the contact are expected in the request’s body as an application/json. via POST /v1/contacts

contacts.write
lexoffice_post_v1_credit_notesWRITE

Credit notes transmitted via the API are created in draft mode per default. To create a finalized credit note with status open the optional query parameter finalize has to be set. The status of a credit note cannot be changed via the api. The created credit note will be shown in the main voucher list in Lexware: https://app.lexware-sandbox.de/vouchers. To provide your customers access to the created credit note please use our deeplink function. via POST /v1/credit-notes

credit-notes.write
lexoffice_post_v1_delivery_notesWRITE

Delivery notes transmitted via the API are created in draft mode per default. To create a finalized delivery note with status open the optional query parameter finalize has to be set. The status of a delivery note cannot be changed via the api. The created delivery note will be shown in the main voucher list in Lexware: https://app.lexware-sandbox.de/vouchers. To provide your customers access to the created delivery note please use our deeplink function. via POST /v1/delivery-notes

delivery-notes.write
lexoffice_post_v1_dunningsWRITE

The created dunning will not be shown in the main voucher list in Lexware, but will be attached to an invoice and will be visible there. To provide your customers access to the created dunning please use our deeplink function. The contents of the dunning are expected in the request's body as an application/json and must not contain read-only fields. via POST /v1/dunnings

dunnings.write
lexoffice_post_v1_event_subscriptionsWRITE

To subscribe to an event, provide the event type and the webhook callback url in the request body. The endpoint returns an action result (HTTP status code 201 Created) on success. Additionally, the Location header returns the resource url. via POST /v1/event-subscriptions

no provider scope
lexoffice_post_v1_invoicesWRITE

Invoices transmitted via the API are created in draft mode per default. To create a finalized invoice with status open the optional query parameter finalize has to be set. The status of an invoice cannot be changed via the api. The created invoice will be shown in the main voucher list in Lexware: https://app.lexware-sandbox.de/vouchers. To provide your end-users access to the created invoice please use our deeplink function. via POST /v1/invoices

invoices.write
lexoffice_post_v1_order_confirmationsWRITE

Order confirmations transmitted via the API are created in draft mode per default. To create a finalized order confirmation with status open the optional query parameter finalize has to be set. The contents of the order confirmation are expected in the request's body as an application/json and must not contain read-only fields. via POST /v1/order-confirmations

order-confirmations.write
lexoffice_post_v1_quotationsWRITE

Quotations transmitted via the API are created in draft mode per default. To create a finalized quotation with status open the optional query parameter finalize has to be set. The status of a quotation cannot be changed via the api. The created quotation will be shown in the main voucher list in Lexware: https://app.lexware-sandbox.de/vouchers. To provide your end-users access to the created quotation please use our deeplink function. via POST /v1/quotations

quotations.write
lexoffice_post_v1_vouchersWRITE

The contents of the voucher are expected in the request's body as an application/json. The contents of the voucher must not contain read-only fields. The created voucher will be shown in the main voucher list in Lexware: https://app.lexware-sandbox.de/vouchers. via POST /v1/vouchers

vouchers.write
lexoffice_put_v1_articles_by_idWRITE

Update an existing article with id {id} with the data given in the payload as JSON. Returns an action result on success. For information about required fields please see Create an article. via PUT /v1/articles/{id}

articles.write
lexoffice_put_v1_contacts_by_idWRITE

Update an existing contact with id {id} with the data given in the payload as JSON. Returns an action result on success. For information about required fields please see Create a contact. via PUT /v1/contacts/{id}

contacts.write
lexoffice_put_v1_vouchers_by_idWRITE

When you have retrieved a voucher via GET that is identified by {id}, it's possible to update or merge it with the latest information of the requesting system, so that e. g. read-only fields will be filled with the latest Lexware information - e.g. id, organizationId and version. Although the voucherStatus attribute reflects the voucher's current (billing) status, it is not possible to change that state using the API, except for the finalization of a voucher from unchecked to open. Apart from that, a voucher with state unchecked may be not updated. via PUT /v1/vouchers/{id}

vouchers.write

Put Lexware Office behind one governed endpoint.

Same permissions, same audit trail, whatever else you connect next.