V2 Integrator API
Trigger Manual Rebalance
Dispatches a one-off rebalance for a portfolio your API key has access to.
POST
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 returns
Common error responses:
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.
- Auth:
x-api-keyheader (required) - Scope:
portfolios:write
operationId 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.
Portfolio identifier returned by
POST /v2/enroll or GET /v2/portfolios.401whenx-api-keyheader is missing or the key is invalid403when the API key lacks theportfolios:writescope404when the portfolio does not exist or your API key cannot access it429when triggered too soon after the previous rebalance — see theRetry-Afterheader500on unexpected server errors