Vezmo App

Billing · Invoices

Send invoice

Emails the invoice, with its PDF and a pay link, to the client again. Creating and updating an invoice already email it; use this when the client needs another copy.

Needs the invoice.send scope. Keys that could create or update invoices when this scope was added were given it, and a new key gets every invoice scope. A key without it gets 403 “Insufficient API permissions” with required: ["invoice.send"].

Authorization

Header

Path parameters

id string Required

The id of the invoice to send.

Good to know

  • PAID and CANCELLED invoices can’t be sent; the call returns 400.
  • data.success is false when the email could not be delivered. A test key's invoice to a client outside your team is sent but not emailed, and that is a success: data is { "success": true, "emailSkipped": "test_mode", "message": "In test mode, emails go only to your team's addresses." }. Check emailSkipped to tell it apart from a delivered email. It doesn't count toward your email limits, and invoice.sent still fires.
  • Each send fires the invoice.sent webhook.

Limits

  • One email per invoice a minute. A second send inside the minute answers 429 “This was emailed moments ago. You can send it again in Ns.”
  • Each business can have Vezmo send 500 invoice and proposal emails in 24 hours, CC copies included (support can set a different number for your business). Past that a send answers 429 “Your business has reached its limit of 500 invoice and proposal emails in 24 hours (CC copies count). You can send more in about N hours. To send more each day, contact support.”
  • The email that Create or Update invoice sends on its own follows the same limits, but never fails the save.