Create recurring invoice schedule
Create a recurring-invoice schedule (contract). Invoices are generated from the schedule’s template on the cadence — occurrence N falls on StartDate plus N intervals (month-end clamped). With AutoSend each occurrence is generated and emailed in one step; otherwise occurrences land as Draft for review. Admin-gated because an AutoSend schedule sends email without further review.
Authentication. An API key (x-dolfin-api-key) together with the x-dolfin-organisation-id header identifying the organisation, or a JWT Bearer token that carries the organisation in its claims.
Authorizations
An API key issued to your client. It carries the client's scope; org-scoped calls also require the x-dolfin-organisation-id header. Keys are created and revoked by a client administrator.
Headers
Target organisation. Required when authenticating with an API key; omit for Bearer callers (resolved from the token).
Body
ISO 4217 currency code (e.g. GBP, USD, EUR)
Payment terms in days (0-365) applied to every generated invoice — the due date is this many days after each occurrence's issue date. 0 means due on receipt. Omit to use the organisation's default payment terms.
Date of the first invoice. Subsequent occurrences fall on this date plus N intervals (month-end clamped).
Weekly, Monthly, Quarterly, Annually Total number of invoices to generate. Omit to run until paused or cancelled.
True: each occurrence is generated and emailed in one step. False: occurrences land as Draft for review.
Response
Created
ISO 4217 currency code (e.g. GBP, USD, EUR)
Payment terms in days applied to every generated invoice. Null means each occurrence uses the organisation's default at generation time.
Weekly, Monthly, Quarterly, Annually When the next invoice will be generated. Null on Paused, Completed, and Cancelled schedules.
Active, Paused, Completed, Cancelled