---
title: "Update schedule"
method: PATCH
path: "/v1/accounts/{accountId}/schedules/{scheduleId}"
tags: ["Schedules"]
---

# Update schedule

`PATCH /v1/accounts/{accountId}/schedules/{scheduleId}`

Update account schedule by schedule ID.

## Request body

- UpdateSchedulerRequest — Request to update an existing schedule
  - `single` object — Single schedule object
    - `description` string — Challenge result
    - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
    - `restrictions` Restrictions — Restrictions applied to the schedule
      - `minimum_daily_available` number, float — Establishes a minimum limit value to always be maintained in the customer's balance. If the value of the customer's balance is lower than the minimum limit value, the schedule is executed, otherwise its execution is stopped and saved as "Executed with restrictions".
      - `minimum_monthly_average_available` number, float — Follows the same logic as `minimum_daily_available`, except it considers an average limit value from the first day of the month until the day before the scheduled execution to compare with the customer’s balance value.
      - `minimum_days_account_inactivity` integer — If the days of account inactivity are greater than this field value, the schedule execution is stopped and saved as "Executed with restrictions".
    - `schedule_details` object — Schedule details
      - `end_date` string, date-time — End date for link (GMT-3). When the final charge for a link is made, `end_date` gets populated.
      - `retries` Retries — Configuration to define retry policy for failed executions.
        - `interval_recurrence` integer — Interval for retries, in minutes
        - `number_of_attempts` integer — Maximum number of execution retries
  - `pre` object — Pre-schedule object
    - `schedule_details` PreScheduleDetails — Pre-schedule details
      - `statement` Statement
        - `id` integer — Pismo ID of the statement linked to the pre-schedule
    - `processing_code` string — Processing code for the debit transaction. If `split_transaction` is `false` (the default), each installment payment is recorded as one debit transaction equal to the installment amount minus the discount, and `processing_code` is the processing code for that transaction. If `split_transaction` is `true`, each installment payment is recorded as two transactions: a debit transaction for the installment amount and a credit transaction for the discount. In this case, `processing_code` is the processsing code for the debit transaction, and `second_processing_code` is the processing code for the credit transaction.
    - `amount` number, double — Fee amount.
    - `currency_code` string — ISO 4217 3-letter currency code, For example, `986` = Brazilian real and `840` = US dollar.
    - `description` string — Challenge result
    - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
  - `transfer` object — Transfer schedule object
    - `description` string — Challenge result
    - `metadata` string — Any data object with key/value pairs. No limit on length. **Note**: This field must not be used to send Personally Identifiable Information (PII), Payment Card Industry (PCI) data, or any sensitive/regulated information. Metadata fields are intended for operational, non-sensitive data only. For sensitive data, use the specific parameters designed for that purpose. For more information, refer to [Get started with Pismo APIs](https://developers.pismo.io/pismo-docs/reference/get-started-with-pismo-apis#metadata).
    - `schedule_details` object — Schedule details
      - `end_date` string, date-time — End date for link (GMT-3). When the final charge for a link is made, `end_date` gets populated.

## Response `204`

No Content

## Other responses

- `400` — Bad request
- `403` — The request has been lost
- `404` — Not Found
- `500` — Internal server error

---

[API](https://skmtc.net/pismo/apis/platform-authentication.md) · [All operations](https://skmtc.net/pismo/apis/platform-authentication/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/pismo/platform-authentication/versions/935b62e16de4/schema)