Actions59
- Document Actions
- Client Actions
- Supplier Actions
- Item (Catalog) Actions
- Expense Actions
- Payment Actions
- Transaction (עסקה) Actions
- Recurring Payment (הוראת קבע) Actions
- Retainer (ריטיינר) Actions
- Accounting Actions
- Business Actions
Recurring Payment (הוראת קבע) → Update
AI-generatedSummary
Update a recurring payment by its UUID, sending the configured document, VAT, schedule, token, and client fields to Morning. Use this to change the details of an existing recurring charge.
Inputs
- Recurring Payment ID (required) — UUID of the recurring payment to update.
- Document Description (required) — Description shown on documents issued for each charge.
- Document Type — Document issued each cycle: tax invoice plus receipt (320, default), tax invoice (305), or receipt (400).
- VAT Type — VAT mode: price before VAT (0, default), VAT included (1), or VAT exempt (2).
- Skip Holidays — Whether to defer a charge that falls on a holiday; the charging day is capped at 25.
- Document Description Rules — Optional dynamic template for the document description.
- End Date — Last charge date. The date is sent as YYYY-MM-DD; leave empty for no date limit.
- Cycles — Number of charges before the order ends. Values above zero are sent; zero or empty is omitted.
- Token ID (required) — UUID of the saved credit-card token to charge.
- Client Email — Email of the client associated with the recurring payment. Empty values are omitted.
- Client ID — Optional UUID of the associated client. Empty values are omitted.
- Request Options — Optional HTTP settings for batching, SSL certificate validation, proxy, and timeout.
Output shape
A single API response item for the updated recurring payment.
The supplied source pack contains no implementation bodies, so the response shape and exact update endpoint cannot be confirmed from the source provided.