import requests
url = "https://api.paywise.de/mahnservice/v1/invoices/{uuid}/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.paywise.de/mahnservice/v1/invoices/{uuid}/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));HttpResponse<String> response = Unirest.get("https://api.paywise.de/mahnservice/v1/invoices/{uuid}/")
.header("Authorization", "Bearer <token>")
.asString();using RestSharp;
var options = new RestClientOptions("https://api.paywise.de/mahnservice/v1/invoices/{uuid}/");
var client = new RestClient(options);
var request = new RestRequest("");
request.AddHeader("Authorization", "Bearer <token>");
var response = await client.GetAsync(request);
Console.WriteLine("{0}", response.Content);
curl --request GET \
--url https://api.paywise.de/mahnservice/v1/invoices/{uuid}/ \
--header 'Authorization: Bearer <token>'{
"access_mode": "production",
"amount": "250.00",
"archived": false,
"balance": "250.00",
"created": "2026-09-02T08:00:00Z",
"currency": "EUR",
"debtor": "72000000-0000-4000-8000-000000000001",
"document": null,
"document_date": "2026-08-18",
"due_date": "2026-09-01",
"dunning_state": "active",
"has_document": false,
"id": "71000000-0000-4000-8000-000000000001",
"invoice_number": "INV-2026-1042",
"overpaid": false,
"paid_amount": "0.00",
"updated": "2026-09-03T09:00:00Z",
"your_reference": "CUSTOMER-1042"
}Get an invoice
Invoices for the public Mahnservice API: the full lifecycle.
Submit creates a held invoice — no dunning process exists until /release creates one. Release enrolls the invoice into the dunning flow (active when the company’s Mahnlauf is activated, pending until then; parked paused under company or debtor holds). PATCH corrects an invoice while it is still held — the only correction window there is, because submit is idempotent on the invoice number and ignores changed fields, and after release the dunning history already references the amount and the due date. Payments, cancel and write-off settle or end the claim. All scoped to the token’s company; the debtor is referenced by UUID.
Write actions apply only to API-submitted invoices; bookkeeping-synced invoices are readable here but owned by their bookkeeping system. Payment reporting stays open through a subscription lapse — a lapsed customer must still be able to stop dunning on a paid invoice.
import requests
url = "https://api.paywise.de/mahnservice/v1/invoices/{uuid}/"
headers = {"Authorization": "Bearer <token>"}
response = requests.get(url, headers=headers)
print(response.text)const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.paywise.de/mahnservice/v1/invoices/{uuid}/', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));HttpResponse<String> response = Unirest.get("https://api.paywise.de/mahnservice/v1/invoices/{uuid}/")
.header("Authorization", "Bearer <token>")
.asString();using RestSharp;
var options = new RestClientOptions("https://api.paywise.de/mahnservice/v1/invoices/{uuid}/");
var client = new RestClient(options);
var request = new RestRequest("");
request.AddHeader("Authorization", "Bearer <token>");
var response = await client.GetAsync(request);
Console.WriteLine("{0}", response.Content);
curl --request GET \
--url https://api.paywise.de/mahnservice/v1/invoices/{uuid}/ \
--header 'Authorization: Bearer <token>'{
"access_mode": "production",
"amount": "250.00",
"archived": false,
"balance": "250.00",
"created": "2026-09-02T08:00:00Z",
"currency": "EUR",
"debtor": "72000000-0000-4000-8000-000000000001",
"document": null,
"document_date": "2026-08-18",
"due_date": "2026-09-01",
"dunning_state": "active",
"has_document": false,
"id": "71000000-0000-4000-8000-000000000001",
"invoice_number": "INV-2026-1042",
"overpaid": false,
"paid_amount": "0.00",
"updated": "2026-09-03T09:00:00Z",
"your_reference": "CUSTOMER-1042"
}Authorizations
Response
A Mahnservice invoice. Created held: no dunning process exists until
POST /invoices/{uuid}/release/ creates one. The debtor is referenced
by UUID and must belong to the same company. Company and environment come
from the token, never the payload. Submitting is idempotent on the
invoice number.
Remaining invoice amount in the invoice currency: amount minus reported payments, with a minimum of zero. Paid, cancelled and written-off invoices report zero. Dunning fees are not included; partial payments do not reduce the amount used in dunning notices.
^-?\d{0,12}(?:\.\d{0,2})?$Current dunning process state. held means an API invoice awaits release; an invoice settled while held reports paid, cancelled, or written_off. Null means a bookkeeping invoice has never been enrolled.
held, pending, active, paused, completed, paid, cancelled, written_off, inkasso 