Getting Started with Postscale Invoices
Overview of Postscale Invoices, prerequisites, and your first validation API call.
Postscale Invoices provides XML preflight checks, UBL invoice generation for email sending, and inbound invoice processing. Start with the validation API reference for a synthetic sample and the exact limits. Preflight checks do not establish full standards conformance or recipient acceptance.
Prerequisites
- A Postscale account with an active plan
- An API key (create one at Dashboard > API Keys)
- A verified domain (required for sending invoices)
Quick Overview
| Capability | Endpoint | Description |
|---|---|---|
| Validate | POST /v1/invoices/validate | Run built-in EN 16931 / XRechnung preflight checks |
| Send | POST /v1/invoices/send | Generate UBL XML and submit it for email delivery |
| Receive | Inbound webhook | Automatically detect and extract e-invoices from incoming email |
Your First Validation Call
The fastest way to try the API is to validate an existing invoice XML:
curl -X POST https://api.postscale.io/v1/invoices/validate \
-H "Authorization: Bearer ps_live_..." \
-H "Content-Type: application/xml" \
--data-binary @invoice.xml
A successful response looks like:
{
"valid": true,
"format": "xrechnung-ubl",
"standard": "EN 16931",
"errors": [],
"warnings": []
}
If the invoice has issues, the errors array will contain detailed descriptions with field paths and rule IDs so you can fix them programmatically.
Next Steps
- Validation API Reference: full request/response details, error codes, and examples
- Sending E-Invoices: generate and deliver XRechnung invoices via the API
- Inbound Processing: automatically detect e-invoices in incoming email
- XRechnung Reference: formats, field mapping, and compliance notes