Skip to main content
The Autopilot screen allows users to view and manage their automations. Users can see their active automations and toggle them on or off.
Top-up and savings automations set up direct debit payments from a linked bank account on a specified day each month. For top-up automations, funds are invested proportionally across the user’s existing holdings. Rebalance automations run monthly against the user’s target allocation and do not use a bank account or mandate.

Data sources

Get Automations

Retrieve all automations for the user, including rebalance automations.

Cancel Automation

Cancel an active automation when user toggles it off.

Prerequisites

  • Backend access to the M2M endpoints
  • Bearer token with required scopes
  • User must have at least one bank account set up (top-up and savings automations)
  • User must have a target allocation set up (rebalance automations)

What to fetch

Use Get automations to retrieve all automations for a user.Returns:
  • Automation ID, status, and category
  • For top-up and savings automations: monthly amount, currency, day of month, and mandate
  • For rebalance automations: category, status, and frequency only
Use Cancel automation when the user toggles off an automation.
  • Sends a POST request to /automations/{id}/cancel
  • Returns 202 Accepted on success
  • Pending deposits not yet submitted will be cancelled

Example: fetch automations

Example: toggle automation off

When a user toggles off an automation, call the cancel endpoint:

Example: enable new automation

To create (enable) a new automation, use the Create automation endpoint.
When creating a top-up or savings automation, a direct debit mandate is created for the specified bank account if one doesn’t already exist. The mandate status is initially Pending until confirmed by the payment provider. Rebalance automations do not create a mandate. The portfolio must already have a target allocation.

See also