How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
lexoffice

lexoffice Vouchers API

Bookkeeping vouchers and the voucherlist search.

Documentation Provider Profile APIs.io OpenAPI GitHub

lexoffice Vouchers API is one of 14 APIs that lexoffice publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Vouchers. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 5 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://api.lexware.io/v1, https://api.lexoffice.io/v1.

5 operations 3 paths 4 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.lexware.io/v1
Authentication
HTTP Bearer
Contact
lexware Office Developers
License
Proprietary
Resource Areas
1

Authentication & Security 1

lexoffice Vouchers API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer API key generated by the account owner at https://app.lexware.de/addons/public-api and passed as Authorization: Bearer YOURAPIKEY.

Paths & Operations 5

Across 3 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Vouchers 5

Bookkeeping vouchers and the voucherlist search.

POST
/vouchers
Create a bookkeeping voucher
createVoucher body → 200400401429
GET
/vouchers/{id}
Retrieve a voucher
getVoucher 1 param → 200401404
PUT
/vouchers/{id}
Update a voucher
updateVoucher 1 param body → 200401404
DELETE
/vouchers/{id}
Delete a voucher
deleteVoucher 1 param → 204401404
GET
/voucherlist
Search the voucher list
listVouchers 6 params → 200401429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Voucher (17 properties), Error (6 properties), VoucherListPage (5 properties), ResourceReference (5 properties). Each schema is shown below with its type and property counts.

ResourceReference
object
5 properties
Error
object
6 properties
VoucherListPage
object
5 properties
Voucher
object
A bookkeeping voucher for preliminary accounting.
17 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lexoffice-vouchers-api-openapi.yml Raw ↑

Other APIs lexoffice publishes across the network.

lexoffice Contacts API
AE Profile APIs.io
lexoffice Credit Notes API
AE Profile APIs.io
lexoffice Delivery Notes API
AE Profile APIs.io
lexoffice Down Payment Invoices API
AE Profile APIs.io
lexoffice Dunnings API
AE Profile APIs.io
lexoffice Event Subscriptions API
AE Profile APIs.io
lexoffice Files API
AE Profile APIs.io
lexoffice Invoices API
AE Profile APIs.io
lexoffice Order Confirmations API
AE Profile APIs.io
lexoffice Payments API
AE Profile APIs.io
lexoffice Profile API
AE Profile APIs.io
lexoffice Quotations API
AE Profile APIs.io
#Vouchers
← Back to L APIs
API Details
ID
lexoffice:lexoffice-vouchers-api
Base URL
https://api.lexware.io/v1
Docs
https://developers.lexware.io/docs/#contacts-endpoint
Provider
lexoffice
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lexoffice-vouchers-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lexoffice-vouchers-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of lexoffice Vouchers API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.