NewThree filters returned the wrong rows
BeeL
Get StartedMulti-NIFVeriFactuStripeAPI ReferenceChangelog
Recurring Invoices

Get the generation history of a recurring invoice

Scopeinvoices:read

Deprecated. Use GET /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/history, which behaves identically.

Returns the invoices previously generated from this recurring template, including their status and generation dates.

GET
/v1/recurring-invoices/{recurring_invoice_id}/history

Authorization

AuthorizationBearer <token>

Keys are prefixed beel_sk_, and each one carries the scopes it was created with: a key short of the scope an operation needs is answered 403. The scope an operation requires is shown next to its title, and the full catalogue lives in the Scopes reference.

Keys are created from the BeeL dashboard. They are secret credentials: do not share them or commit them to source control.

In: header

Path Parameters

recurring_invoice_idstring
Formatuuid

Response Body

application/json

application/json

application/json

application/json

curl -X GET "https://app.beel.es/api/v1/recurring-invoices/497f6eca-6276-4993-bfeb-53cbbbba6f08/history"
{
  "success": true,
  "data": {
    "history": [
      {
        "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
        "invoice_id": "f4c4edb8-11e0-4b33-bcc1-482dc59ebb32",
        "generated_at": "2019-08-24T14:15:22Z",
        "scheduled_date": "2019-08-24"
      }
    ]
  },
  "meta": {
    "timestamp": "2025-01-15T10:30:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
{
  "success": false,
  "error": {
    "code": "FORBIDDEN",
    "message": "You do not have permission to access this resource"
  },
  "meta": {
    "timestamp": "2025-01-15T10:30:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
{
  "success": false,
  "error": {
    "code": "NOT_FOUND",
    "message": "Resource not found"
  },
  "meta": {
    "timestamp": "2025-01-15T10:30:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}
{
  "success": false,
  "error": {
    "code": "UNSUPPORTED_MEDIA_TYPE",
    "message": "Unsupported media type: text/plain. Supported: application/json"
  },
  "meta": {
    "timestamp": "2025-01-15T10:30:00Z",
    "request_id": "4bf92f3577b34da6a3ce929d0e0e4736"
  }
}

Preview the next invoice of a recurring template GET

**Deprecated.** Use `GET /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}/next-occurrence`, which behaves identically. Returns the invoice that would be produced by the next generation of this recurring template, computed from the current issuer, recipient and series data. Nothing is persisted.

Replace a recurring invoice PUT

**Deprecated.** The canonical form has a single update verb, `PATCH /v1/companies/{company_id}/recurring-invoices/{recurring_invoice_id}`, which is not a drop-in replacement: it changes only the fields present in the body. To reproduce a total replacement, send every field and pass `null` in the ones you want cleared. Replaces the schedule, template lines and recipient of a recurring invoice with the body you send. Only allowed while the template is active or paused. - **Not a partial update:** leaving out `end_date`, `payment_method` (with its `payment_iban`, `payment_swift` and `payment_term_days`), `notes` or `email_configuration` clears them. - **`lines`:** replaced as a whole. Omitting them or sending `null` keeps the current ones, and an empty array is rejected. - **`verifactu_enabled`:** the exception to the rule — omitting it leaves the current value untouched, it is never read as "turn it off". Send `false` explicitly to disable VeriFactu.