---
title: "Connect your app to Lexware"
description: "<p><a href=\"https://www.lexware.de/\">Lexware</a> is an accounting and invoicing platform for managing business contacts, documents, vouchers, payments, and bookkeeping workflows."
---

> Documentation Index
> Fetch the complete documentation index at: https://rshift.helpcent.re/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect your app to Lexware

<p><a href="https://www.lexware.de/">Lexware</a> is an accounting and invoicing platform for managing business contacts, documents, vouchers, payments, and bookkeeping workflows. The Lexware connector lets your RShift Sites app call the Lexware API through a connected Lexware account. It's designed for apps that need to read or manage operational accounting data from Lexware.</p>
<p>Lexware is available as an <a href="/sites/integrations/app-connectors/">app + chat connector</a>: one shared connection that works in the project chat while you build and in your published apps.</p>
<p>With Lexware, your app can:</p>
<ul>
<li>Read company profile and accounting settings</li>
<li>Create and retrieve contacts, articles, invoices, quotations, and vouchers</li>
<li>Download generated accounting documents, such as invoice PDFs</li>
<li>React to invoice, payment, and contact changes with Lexware event subscriptions</li>
<li>Build bookkeeping, sales, and finance workflows around Lexware business data</li>
</ul>
<p>Lexware is a good fit when your app needs accounting data, document workflows, or back-office automation connected to a Lexware account.</p>
<h2>Common use cases and example apps</h2>
<p>These examples show what you can build with Lexware, each with a prompt to start from.</p>
<table>
<thead>
<tr>
<th style="text-align: left">Example app</th>
<th style="text-align: left">Example prompt</th>
<th style="text-align: left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td style="text-align: left"><strong>Invoice operations dashboard</strong></td>
<td style="text-align: left"><em>Use Lexware and build a dashboard that lists open invoices, payment status, and customer details.</em></td>
<td style="text-align: left"><strong>Track invoice work from one internal view.</strong><br />The app fetches invoice and contact data from Lexware so finance teams can review outstanding work.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Customer accounting portal</strong></td>
<td style="text-align: left"><em>Use Lexware and build a customer portal that shows invoices, quotations, and downloadable PDFs.</em></td>
<td style="text-align: left"><strong>Give customers access to accounting documents.</strong><br />The app retrieves the right documents from Lexware and presents them in a branded portal.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Voucher intake workflow</strong></td>
<td style="text-align: left"><em>Use Lexware and build a voucher upload and review workflow for incoming expenses.</em></td>
<td style="text-align: left"><strong>Move expense intake into a guided app.</strong><br />The app creates or retrieves voucher records in Lexware and helps operators review missing details.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Contact management tool</strong></td>
<td style="text-align: left"><em>Use Lexware and build an internal tool for searching and updating business contacts.</em></td>
<td style="text-align: left"><strong>Keep customer and supplier records accessible.</strong><br />The app reads contact records from Lexware and gives teams a focused interface for finance-related customer data.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Sales quote tracker</strong></td>
<td style="text-align: left"><em>Use Lexware and build a quotation tracker that shows quote status and related contacts.</em></td>
<td style="text-align: left"><strong>Monitor quotes before they become invoices.</strong><br />The app retrieves quotations and related contact data from Lexware for sales and finance follow-up.</td>
</tr>
<tr>
<td style="text-align: left"><strong>Accounting event monitor</strong></td>
<td style="text-align: left"><em>Use Lexware and build an event monitor for invoice, payment, and contact changes.</em></td>
<td style="text-align: left"><strong>React to Lexware changes in app workflows.</strong><br />The app uses event subscriptions to receive change notifications and then fetches updated resources from Lexware.</td>
</tr>
</tbody>
</table>
<h2>How to connect Lexware</h2>
<p>Who can create Lexware connections depends on your plan and workspace settings. App + chat connectors are available by default on Free, Pro, and Business plans. On Enterprise plans, they are effectively disabled at first: <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a> defaults to <strong>No one</strong> until an admin changes it in <strong>Connectors → Admin settings → App + chat connectors</strong>.</p>
<p>You can create multiple Lexware connections using different API keys, which is useful for separating environments (for example, development and production) or connecting different Lexware accounts.</p>
<p>When the connection is created, you can <a href="/sites/integrations/app-connectors/#link-a-connection-to-a-project">link it to the projects</a> where you want to use it. Anyone building in a project can ask RShift Sites in the project chat to link their project to it.</p>
<h3>Prerequisites</h3>
<p>Before connecting Lexware, make sure you have:</p>
<ul>
<li>A Lexware account with access to the public API</li>
<li>A Lexware public API key</li>
<li>Permission to <strong>create connections</strong> in your RShift Sites workspace (see <a href="/sites/integrations/admin-controls/#who-can-create-connections-and-clients">Who can create connections and clients</a>)</li>
</ul>
<blockquote>
<p><strong>Note</strong></p>
<p>All API requests made through this connector use your Lexware API key. API usage, plan limits, and billing are handled directly by Lexware, not RShift Sites.</p>
</blockquote>
<h3>Step 1: Get a Lexware API key</h3>
<p>A Lexware public API key lets your RShift Sites app authenticate with the Lexware API. You can create separate keys for different environments or apps.</p>
<p>To create a Lexware API key:</p>
<p><strong>Open the Lexware public API page</strong></p>
<p>Sign in to Lexware and open the <a href="https://app.lexware.de/addons/public-api">Public API page</a>. If Lexware asks you to sign in first, complete the sign-in and open the link again.</p>
<p><strong>Create an API key</strong></p>
<p>Generate a public API key. If Lexware asks for a name, use a descriptive one, for example <code>RShift Sites integration</code>.</p>
<p><strong>Copy the key</strong></p>
<p>Copy the API key and store it securely.</p>
<blockquote>
<p><strong>Danger</strong></p>
<p>Your API key functions like a password. Keep it secure and never share it publicly. You'll need it in the next step.</p>
</blockquote>
<p>See Lexware documentation for more: <a href="https://developers.lexware.io/docs/">Lexware API documentation</a>.</p>
<h3>Step 2: Connect Lexware to RShift Sites</h3>
<p>You can create multiple connections using different API keys.</p>
<p><strong>Open Lexware in Connectors</strong></p>
<p>Open <a href="https://lovable.dev/dashboard?connectors"><strong>Connectors</strong></a> and select <strong>Lexware</strong>. For the other places to open the catalog from, see <a href="/sites/integrations/introduction/#where-to-find-connectors">Where to find connectors</a>.</p>
<p><strong>Add a connection</strong></p>
<p>Click <strong>Add connection</strong>.</p>
<p><strong>Configure the connection</strong></p>
<ol>
<li><strong>Display name</strong>: name the connection, for example <code>Lexware Prod</code>. This name is only used inside RShift Sites to identify the connection.</li>
<li><strong>API key</strong>: paste your Lexware public API key.</li>
</ol>
<p><strong>Choose who can use this connection</strong></p>
<p>Under <strong>Sharing</strong>, the connection is private to you by default and shows a <strong>Private</strong> label. To share it, click <strong>Share with others</strong>. Then add workspace members by email, or click <strong>Invite entire workspace</strong> to make the connection available to everyone in your RShift Sites workspace.</p>
<pre><code>See [Who can use connections and clients](/sites/integrations/admin-controls/#who-can-use-connections-and-clients) for more information.
</code></pre>
<p><strong>Connect</strong></p>
<p>Click <strong>Connect</strong>. RShift Sites verifies the key against the Lexware API before saving the connection.</p>
<p>When connected, anyone building in a project can ask RShift Sites in the project chat to link their project to Lexware (based on configured connection-level access). Your RShift Sites apps can then work with Lexware accounting, contact, invoice, quotation, voucher, and article data.</p>
<h2>Working with Lexware event subscriptions</h2>
<p>Lexware supports event subscriptions for change notifications, including invoice, payment, contact, article, voucher, quotation, and related document events.</p>
<p>When you ask RShift Sites to build webhook-based Lexware workflows, your app needs a public HTTPS callback endpoint. Lexware sends event notifications to that endpoint and signs each one. The app verifies the signature and then fetches the changed resource from Lexware.</p>
<blockquote>
<p><strong>Note</strong></p>
<p>Lexware allows up to 2 requests per second per client across all endpoints. Ask RShift Sites to use pagination where available, avoid parallel requests, and retry rate-limit responses with backoff.</p>
</blockquote>
<h2>Limitations</h2>
<p>The Lexware connector cannot:</p>
<ul>
<li>Create a Lexware account or API key for you.</li>
<li>Rotate API keys automatically. To rotate a key, generate a new key in Lexware and update the RShift Sites connection.</li>
<li>Keep event subscriptions working after the Lexware API key changes. Lexware removes the subscriptions created with a key when that key is invalidated, so re-create them after updating the connection with a new key.</li>
<li>Support per-end-user Lexware login. Each connection represents a single Lexware account shared across all projects linked to it.</li>
</ul>
<h2>Manage your {connector_0} connection</h2>
<p>Connections are managed from <a href="https://lovable.dev/dashboard?connectors"><strong>Connectors</strong></a>: select <strong>{connector_0}</strong>, then open the connection.</p>
<ul>
<li><strong>Unlink projects</strong> to remove {connector_0} access from specific projects while keeping the connection available for others. See <a href="/sites/integrations/app-connectors/#unlink-projects-from-a-connection">Unlink projects from a connection</a> for the steps.</li>
<li><strong>Delete the connection</strong> to remove it from the workspace entirely. Deleting is permanent. It removes the credentials from all linked projects, and app features that use {connector_0} stop working until a new connection is added. See <a href="/sites/integrations/app-connectors/#delete-a-connection">Delete a connection</a> for the steps and who can delete.</li>
</ul>
<h2>Related topics</h2>
<ul>
<li><a href="/sites/integrations/workday/">Connect your app to Workday</a></li>
<li><a href="/sites/integrations/notion/">Connect your app to Notion</a></li>
<li><a href="/sites/integrations/granola/">Connect your app to Granola</a></li>
<li><a href="/sites/integrations/slack/">Connect your app to Slack</a></li>
<li><a href="/sites/integrations/inngest/">Connect your app to Inngest</a></li>
</ul>

Source: https://rshift.helpcent.re/sites/integrations/lexware/index.mdx
