Create and email UBL invoices
Send your invoice data as JSON and your customer receives a validated UBL invoice from your own address, for example [email protected]. Peppol BIS Billing by default, or the profile you choose, created, checked and emailed in a single API call.
Built for teams whose buyers import UBL into their accounting system: the XML arrives by email under your name, already checked against EN 16931 and the rules of its profile.
{
"status": "accepted",
"messageId": "0100019a2f4c8e1b-3d7a9c52-..."
}
One call: created, checked and sent
No mail server to run and no attachment handling in your code. The API builds the XML exactly as POST /v1/create/ubl does, and emails it only when it passes.
Validated before it is sent
The invoice is generated and checked against the official rules. If a rule fails, you get the findings back and no email goes out.
From your own domain
The email comes from an address on your verified domain, such as [email protected], with your subject and message in any language. Replies reach your team.
No copy kept
No copy of the attached invoice or of your subject and message is kept. The response carries a message id that you keep on your side.
Your finance team in copy
Add cc and bcc addresses, such as [email protected] or your accountant, and the same email reaches them in the same call. Bcc addresses stay hidden from your customer.
Set up once, then send with every invoice
Your invoices go out from your own domain, so your customers see your name and their replies reach your team. The domain is set up once in your dashboard.
Add your domain
Open Verified email domains in your dashboard and add your domain, or a subdomain such as mail.yourcompany.com.
Publish three DNS records
Copy the three CNAME (DKIM) records to your DNS provider. The status turns to Verified, usually within minutes and at most 72 hours later.
Send with one call
Call an email endpoint with your invoice and the email details. Any address on the domain works as the sender, for example [email protected].
See pricing for the plans that include email delivery.
The whole request
The same JSON body as POST /v1/create/ubl, plus an email object. The answer is the delivery status instead of the file.
$ curl -X POST https://api.invoicexml.com/v1/create/ubl/email \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "invoice": { "invoiceNumber": "2026-0042", ... }, "email": { "from": "[email protected]", "fromName": "Your Company Billing", "to": "[email protected]" } }'
Need the XML back in the response instead, for your own delivery or archive? Use POST /v1/create/ubl.
Email Delivery
Create or embed a compliant e-invoice and email it to your customer from your own domain, in one call.
Create and email ZUGFeRD
Create a ZUGFeRD PDF/A-3 from JSON and email it from your own domain.
Create and email Factur-X
Create a Factur-X PDF/A-3 from JSON and email it from your own domain.
Create and email XRechnung
Create an XRechnung from JSON and email the XML from your own domain.
Create and email UBL
Create a UBL invoice from JSON and email the XML from your own domain.
Create and email CII
Create a CII invoice from JSON and email the XML from your own domain.
Embed and email Factur-X
Embed your CII XML into your own PDF as Factur-X and email the result.
Embed and email ZUGFeRD
Embed your CII XML into your own PDF as ZUGFeRD and email the result.
Frequently Asked Questions
How do I send from my own address?
Add your domain, or a subdomain, on the Verified email domains page of your dashboard and publish the three DNS records it shows at your DNS provider. Verification usually takes a few minutes and can take up to 72 hours. From then on you can send from any address on that domain, for example [email protected].
What does email delivery cost?
Each successful call costs one credit, like every other endpoint. The pricing page lists the plans that include email delivery and how many sending domains each one has. Calls that send nothing because of a plan or email setting are not billed.
Is the invoice checked before it is sent?
Yes. The invoice is created and validated exactly as on POST /v1/create/ubl. An invoice with errors comes back with its findings, and no email is sent.
What does my customer receive?
An email from your address with the UBL XML attached as invoice-{number}.xml (credit-note-{number}.xml for a credit note), and your own subject and message in any language. Leave them out and a short English subject and message naming the invoice number are used.
Can my finance department get a copy?
Yes. Add cc or bcc addresses to the email, for example [email protected] or your accountant's address, and the same email with the invoice reaches them in the same call. Bcc addresses stay hidden from your customer.
Do you keep a copy of the email?
InvoiceXML keeps no copy of the attached invoice or of your subject and message. The message id is listed with the call in your API logs. If an email bounces or the recipient marks it as spam, that recipient address is kept so it is not emailed again.
Ready to automate your invoices?
Validate, convert and embed compliant e-invoices through one API. Start your 30-day free trial. No credit card required.