Send invoice via email
Sends an invoice to the customer via email as a PDF attachment. The invoice must have a contact with a valid email address set.
What happens when you send an invoice:
- Invoice PDF document is generated
- Invoice status changes from “New” to “Sent”
- Sending date (
sentAt) is recorded as the current date - Sending type is set to “Email” (indicating email sending)
- Contact recipient is recorded (from invoice contactId)
- Payment due date (
dueDate) is calculated based on:- Organization-specific payment terms (
invoiceDueDays), or - Workspace default payment terms (
defaultInvoiceDueDays)
- Organization-specific payment terms (
- Status change timestamp and user are recorded
- Email is sent to the contact’s email address with PDF attachment
- The payment term starts running from this point
Important restrictions:
- Only invoices with status “New” or “Sent” can be sent
- Invoices that are “Paid” or “Cancelled” cannot be sent
- The invoice must have a contact with a valid email address
- Use POST /billing/setInvoiceContactId to set the contact if needed
Use cases:
- Send invoice to customer via email
- Automate invoice delivery
- Track invoice sending and payment terms
What is returned:
- Success response confirming the invoice was sent
POST
/billing/invoices/sendInvoiceAuthorization
AuthorizationOAuth2 access token · headerrequiredScopes:
api:writeor
AuthorizationBearer token (JWT) · headerrequiredRequest body
requiredapplication/jsonInvoice ID to send
idstring<uuid>requiredInvoice ID (UUID) to send. The invoice must have a contact with a valid email address set. The invoice will be sent via email as a PDF attachment.
Responses
200
Invoice sent successfully
successbooleanrequiredOperation success flag
400
Invoice cannot be sent (only invoices with status "New" or "Sent" can be sent, or contact email is missing)
401
Unauthorized - Invalid or missing authentication token
403
Forbidden - Insufficient API scopes or permissions
404
Invoice not found