---
title: "Staking"
description: "This section describes the API-driven staking operating model for institutional client integrations."
url: "https://docs.api.galaxy.com/guides/staking"
image: "https://docs.api.galaxy.com/_og/d/c_Ocean.takumi,title_Staking,description_This+section+describes+the+API-driven+staking+operating+model+for+institutional+client+integrations.,props_eyJ0aGVtZSI6eyJtb2RlIjoiZGFyayIsImNvbG9ycyI6eyJwcmltYXJ5IjoiI2ZmNWExZiJ9fX0,p_Ii9ndWlkZXMvc3Rha2luZyI,s_D6ZYnWarPLVfvhgk.png"
---

# Staking

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

## [API Reference](#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](https://docs.api.galaxy.com/apis).

## [Family Navigation](#family-navigation)

-   Coming Soon

## [Staking Model](#staking-model)

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

Typical flow:

1.  Client submits stake request.
2.  Position is created and progresses through lifecycle states.
3.  On-chain confirmation occurs.
4.  Client receives lifecycle events.
5.  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](#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](#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](#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](#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](#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.