Update a recurrence
Request
- Base URL: https://api.sandbox.monite.com/v1
- URL: https://api.sandbox.monite.com/v1/recurrences/{recurrence_id}
- Auth: HTTP bearer
Path parameters
Headers
The ID of the entity that owns the requested resource.
Request body
Automation level for recurrence
The end date of the recurring invoice, in the yyyy-mm-dd format. The end date is inclusive, that is, the last invoice will be created on this date if the last occurrence falls on this date. end_date is mutually exclusive with max_occurrences. Either end_date or max_occurrences must be specified.
Deprecated, use end_date instead
Deprecated, use end_date instead
The interval between each occurrence of the invoice. For example, when using monthly frequency, an interval of 1 means invoices will be created every month, an interval of 2 means invoices will be created every 2 months.
How many times the recurring invoice will be created. The recurrence will stop after this number is reached. max_occurrences is mutually exclusive with end_date. Either max_occurrences or end_date must be specified.
The date when the first invoice will be created, in the yyyy-mm-dd format. Cannot be a past date. Subsequent invoice dates will be calculated based on start_date, frequency, and interval.
Response
Successful Response
Time at which the recurrence was created. Timestamps follow the ISO 8601 standard.
Time at which the recurrence was last updated. Timestamps follow the ISO 8601 standard.
Automation level for recurrence
The body text for the email that will be sent with the recurring invoice.
Current iteration number
The end date of the recurring invoice, in the yyyy-mm-dd format. The end date is inclusive, that is, the last invoice will be created on this date if the last occurrence falls on this date. end_date is mutually exclusive with max_occurrences. Either end_date or max_occurrences must be specified.
Deprecated, use end_date instead
Deprecated, use end_date instead
The interval between each occurrence of the invoice. For example, when using monthly frequency, an interval of 1 means invoices will be created every month, an interval of 2 means invoices will be created every 2 months.
ID of the base invoice that will be used as a template for creating recurring invoices.
How many times the recurring invoice will be created. The recurrence will stop after this number is reached. max_occurrences is mutually exclusive with end_date. Either max_occurrences or end_date must be specified.
The date when the first invoice will be created, in the yyyy-mm-dd format. Cannot be a past date. Subsequent invoice dates will be calculated based on start_date, frequency, and interval.
Deprecated, use start_date instead
Deprecated, use start_date instead
Represents the status of a recurrence
Allowed transitions:
- active -> paused
- active -> canceled
- active -> completed
- paused -> active
- paused -> canceled
The subject for the email that will be sent with the recurring invoice.
Changes
No recorded changes to this operation across all 1 revision of this API.