Skip to main content
PATCH
/
autopay
/
{autopay_id}
Update an autopay schedule
curl --request PATCH \
  --url https://api.montereyfinancial.app/autopay/{autopay_id} \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "payment_method_id": "<string>",
  "amount_cents": 1,
  "end_date": "2023-12-25"
}
'
{
  "id": "<string>",
  "account_id": "<string>",
  "payment_method_id": "<string>",
  "amount_cents": 123,
  "frequency_unit": "<string>",
  "frequency_interval": 123,
  "start_date": "2023-12-25",
  "next_run_date": "2023-12-25",
  "status": "<string>",
  "created_at": "2023-11-07T05:31:56Z",
  "updated_at": "2023-11-07T05:31:56Z",
  "anchor_day": 123,
  "anchor_month": 123,
  "end_date": "2023-12-25",
  "cancelled_at": "2023-11-07T05:31:56Z"
}

Authorizations

Authorization
string
header
required

Static API key issued via the client portal. Treat it like a password.

Path Parameters

autopay_id
string
required

Body

application/json

Editable autopay fields. Cadence and start date are fixed once created — cancel and recreate the schedule to change them.

payment_method_id
string | null

Switch the schedule to a different stored payment method. Must belong to a borrower on the schedule's account.

amount_cents
integer | null

New per-run amount, in integer cents.

Required range: x > 0
end_date
string<date> | null

New last date a run may occur.

status
enum<string> | null

Pause or resume the schedule. Cancelling is done via DELETE.

Available options:
active,
paused

Response

Successful Response

A recurring payment schedule tying an account to a stored payment method.

id
string
required
account_id
string
required

The account this schedule pays toward.

payment_method_id
string
required

The stored payment method charged on each run.

amount_cents
integer
required

Amount charged per run, in integer cents.

frequency_unit
string
required

Unit of the recurrence interval. One of: day, week, month, year.

frequency_interval
integer
required

Number of units between runs (e.g. 2 + week = every two weeks).

start_date
string<date>
required

Date of the first scheduled run.

next_run_date
string<date>
required

Date the next charge is scheduled to run.

status
string
required

Schedule state. One of: active, paused, cancelled, expired.

created_at
string<date-time>
required
updated_at
string<date-time>
required
anchor_day
integer | null

Day of month (1-31) runs are pinned to, for month/year cadences. Clamped to the last day of shorter months.

anchor_month
integer | null

Month (1-12) runs are pinned to, for yearly cadences.

end_date
string<date> | null

Last date a run may occur. Null for open-ended schedules.

cancelled_at
string<date-time> | null

When the schedule was cancelled. Null unless cancelled.