GET /v1/invoices/{}/document → endpoint removal
Lexware Office APIDeprecated, no date
Lexware Office deprecated the GET /v1/invoices/{}/document endpoint on August 13, 2025, without announcing a shutdown date. The provider states that this endpoint should no longer be used. Calls to this endpoint will eventually fail once it is removed.
Calls it hits
GET /v1/invoices/{}/document
What to use instead of these calls
Download the PDF with GET /v1/invoices/{id}/file instead.
In Lexware Office API's words
This endpoint is deprecated and should no longer be used. Instead, use the invoice file subresource to directly download the document by specifying the id of the invoice.
Facts
- API
- Lexware Office API
api.lexware.io - Kind
- Endpoint removal
- Announced
- August 13, 2025
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Lexware Office API's own pages
Questions
When does this change take effect?
Lexware Office API deprecated GET /v1/invoices/{}/document without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Lexware Office API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Lexware Office API 5
-
No date
GET /v1/credit-notes/{}/documentEndpoint removal Deprecated, no date -
No date
GET /v1/delivery-notes/{}/documentEndpoint removal Deprecated, no date -
No date
GET /v1/dunnings/{}/documentEndpoint removal Deprecated, no date -
No date
GET /v1/order-confirmations/{}/documentEndpoint removal Deprecated, no date -
No date
GET /v1/quotations/{}/documentEndpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.