Skip to main content
POST
Reactivate a recurring invoice
Authentication: API key OAuth 2.0
Scope: client_invoice.write
Generation resumes at the next scheduled date, which the response shows again as next_invoice_date. Invoices skipped during the suspension are not generated. Only a suspended recurring invoice can be reactivated. scheduled, active, canceled and finished all return 412 recurring_invoice_status_transition_forbidden. A suspended recurring invoice whose end_date has passed becomes finished and cannot be reactivated. Takes no request body.

Authorizations

Authorization
string
header
required

Bearer authorization header: Bearer <token>, where <token> is the access token received from the authorization server at the end of the OAuth 2.0 flow.

Headers

X-Qonto-Staging-Token
string

Required only for Sandbox API requests; to get one, please sign up to the Developer Portal.

Path Parameters

id
string<uuid>
required

The unique identifier of the recurring invoice.

Response

The recurring invoice, now active.

recurring_invoice
object
required