Accounting
Connect Lexware Office
Your application calls one EchoRelay URL. When Lexware Office changes its API, you update the mapping, not your application.
How Lexware Office signs requests
An API key from your Lexware account, sent as a bearer token in the Authorization header.
Can you connect it today?
Yes. Add a bearer-token credential with your Lexware API key.
A sample mapping
Your application sends the first request below. The mapping turns it into the body of POST /v1/articles, shown second.
Your request
{
"name": "Support hours",
"unit": "Stunde",
"netPrice": 90,
"vatRate": 19
}
What Lexware Office receives
{
"title": "Support hours",
"type": "SERVICE",
"unitName": "Stunde",
"price": {
"netPrice": 90,
"leadingPrice": "NET",
"taxRate": 19
}
}
The mapping
{
"$schema": "https://schemas.echorelay.dev/transform/mapping/v1.json",
"root": {
"type": "object",
"id": "root",
"properties": {
"title": {
"type": "field",
"id": "title",
"path": "name"
},
"type": {
"type": "constant",
"id": "type",
"value": "SERVICE"
},
"unitName": {
"type": "field",
"id": "unit",
"path": "unit"
},
"price": {
"type": "object",
"id": "price",
"properties": {
"netPrice": {
"type": "field",
"id": "net-price",
"path": "netPrice"
},
"leadingPrice": {
"type": "constant",
"id": "leading-price",
"value": "NET"
},
"taxRate": {
"type": "field",
"id": "tax-rate",
"path": "vatRate"
}
}
}
}
}
}
The grammar, the answer mapping and the dry run are in the mapping docs.
What you bring
This is not a ready-made connector. You bring a sample request or Lexware Office’s OpenAPI document, you or your agent write the mapping, and we run the integration you define.
Lexware Office facts on this page were read 2026-10-29 from Lexware API documentation. Another service? Check it here.
Connect everything. Deploy nothing.
No credit card required.