Skip to main content
GET
Returns the current lifecycle state of an operation previously dispatched via a write endpoint such as POST /v2/portfolios/{portfolioId}/withdraw or POST /v2/portfolios/{portfolioId}/rebalance. Use to poll for onchain confirmation. Operations transition through:
completed, failed, and cancelled are terminal — stop polling once you see one.
  • Auth: x-api-key header (required)
  • Scope: portfolios:read

Polling cadence

Poll at 2–5 second intervals. There is no SLA on when a dispatched withdrawal confirms onchain — it depends on the target chain’s block time, bundler throughput, and paymaster availability. For withdraws, typical end-to-end latency is under a minute on Base / Arbitrum / Polygon and under ~30 seconds on L1 in most conditions; but pathological conditions (RPC congestion, paymaster rebalancing) may push this higher.

Response fields

Common error responses:
  • 401 when x-api-key header is missing or the key is invalid
  • 403 when the API key lacks the portfolios:read scope
  • 404 when the portfolio doesn’t exist, your API key cannot access it, or the operationId doesn’t correspond to any operation on that portfolio
  • 500 on unexpected server errors