Staking

This section describes the API-driven staking operating model for institutional client integrations.

API Reference

Browse the interactive OpenAPI reference for the Staking APIs — endpoints, request and response schemas, authentication, and in-browser “Try it” — in the API catalog.

Coming Soon

Staking Model

Staking integration is designed around lifecycle-managed positions, event notifications, and reconciliation-ready state transitions.

Typical flow:

Client submits stake request.
Position is created and progresses through lifecycle states.
On-chain confirmation occurs.
Client receives lifecycle events.
Rewards accrue and are reported through position/reward views.

Unstaking follows an analogous lifecycle until assets return to available state according to product/network behavior.

Event-Driven Pattern

Treat webhook processing as a first-class component:

Process lifecycle events for stake and unstake confirmations
Process epoch/reward events where supported
Reconcile event stream with API-read state for operational correctness

Security and Controls

Verify webhook signatures and claims
Enforce replay-safe processing
Use idempotency for stake/unstake write paths where supported
Persist auditable state transitions for operations and reporting

Coverage Note

Current supplied examples for staking lifecycle and reward detail are Solana-focused. Avoid claiming broader asset/network behavior until confirmed in product documentation.

Integration Priorities

Position state mapping into client portfolio/accounting systems
Reward visibility and reporting consistency
Exception handling for delayed lifecycle transitions
Operational alerts for event ingestion and reconciliation mismatches

Control Background

Webhook signature verification and replay-safe processing are part of the operating model.
Idempotency is required for stake and unstake write paths where supported.
Auditable state transitions should be retained for operations and reporting.