Dispatches a one-off rebalance for a portfolio your API key has access to.
Dispatches a one-off rebalance run outside the portfolio’s schedule. Typical use cases: an end-user wants to re-target immediately to capture or hedge market volatility, or your UI exposes a “rebalance now” control. The endpoint returnsDocumentation Index
Fetch the complete documentation index at: https://docs.glider.fi/llms.txt
Use this file to discover all available pages before exploring further.
202 immediately with an operationId; poll
GET /v2/portfolios/{portfolioId}/operations/{operationId} until the
operation completes (state: completed, failed, or cancelled).
To decide when (or whether) to surface a manual trigger, read nextDueAt
and lastRebalanceAt from GET /v2/portfolios/{portfolioId} first.
x-api-key header (required)portfolios:writeoperationId and original submittedAt from the
in-flight run. Treat operationId as an opaque token.
Each portfolio has a cooldown between manual triggers. Calls that arrive
too soon after the previous rebalance return 429 with a Retry-After
header (in seconds) indicating when to retry.
Returns 404 for portfolios your API key does not have access to —
same response shape as a portfolio that doesn’t exist.
POST /v2/enroll or GET /v2/portfolios.401 when x-api-key header is missing or the key is invalid403 when the API key lacks the portfolios:write scope404 when the portfolio does not exist or your API key cannot access it429 when triggered too soon after the previous rebalance — see the Retry-After header500 on unexpected server errors