Skip to main content
Glider automation keeps a portfolio aligned with its strategy’s target allocation. B2B API automation is chain-agnostic. The same routes work for supported EVM and Solana portfolios. All write routes require the portfolios:write scope.

Inspect the schedule

GET /v2/portfolios/{portfolioId} returns the current schedule. The object includes status, frequency, intervalMs, nextDueAt, and lastRebalanceAt. A portfolio can have a null schedule.

Start or resume automation

This request does not change a schedule that is active. For a paused schedule, the request resets nextDueAt. The scheduler can then run it on the next cycle. A portfolio without a schedule returns 400.

Pause automation

This request does not change a portfolio that is paused. It keeps the rebalance history and the onchain state.

Trigger one rebalance

The route returns 202 and starts an asynchronous operation. A short cooldown prevents duplicate manual triggers for the same portfolio.

Poll the operation

Poll every 2–5 seconds. Stop when state is completed, failed, or cancelled. Usually, the state changes from accepted to running and then to a final state. See the endpoint references for start, stop, manual rebalance, and operation status.

Operational guidance

  • Keep API keys on your backend.
  • Treat a rebalance as asynchronous. Poll the returned operation.
  • Respect Retry-After when manual rebalances return 429.
  • Read the portfolio again after each change. Do not keep a separate schedule state in the client.
  • Monitor failed operations before attempting another rebalance.