# Invoice PDF generated API Reference

Delivered when BeeL. stores the PDF of an invoice.

**Trigger:**
- **Issued invoice:** once. The PDF of an issued invoice is generated a single time — with
  its VeriFactu QR when the issuer uses VeriFactu, at issuance otherwise — and is never
  modified afterwards. Voiding the invoice or issuing a corrective for it does **not**
  produce a new PDF and does not deliver this event: the status is reported by the API
  and by `invoice.voided`, not by the document.
- **Proforma:** each time its PDF is generated (created, or regenerated after an edit).
- **Exceptional regeneration:** BeeL. staff may regenerate the PDF of an issued invoice
  to fix a rendering defect. That is recorded and delivers the event again, with the next
  `data.generation`. It never sends an email to the customer.

`data.generation` numbers the stored PDF of that invoice (`1`, `2`, …). Each generation is
delivered once: a redelivery of the same generation is a retry, not a new PDF, and carries
the same `BeeL-Event-Id`.

**Recommended actions:**
- Re-fetch the PDF with `GET /v1/companies/{company_id}/invoices/{invoice_id}/pdf`, which
  returns a fresh pre-signed URL. That call now waits for the PDF instead of making you
  poll, so a `200` is the normal answer.
- Drop any copy you cached from an earlier delivery of this same invoice.

**No URL travels in the payload** — on purpose. A download URL expires in five minutes and
webhooks are retried for longer than that, so a delivered URL would often be dead on
arrival and, until then, sitting in your logs.

**Always verify `BeeL-Signature` before processing.**


> Not rendered here (no operation matched this page) — see the full OpenAPI spec at https://docs.beel.es/api/openapi


---

Full OpenAPI spec: https://docs.beel.es/api/openapi