Skip to main content

API Overview

Pine Stake exposes two public HTTP surfaces used by pinestake.com:

Base URLRole
https://api.pinestake.comCore backend — validators, stake pools, staking metrics, sandwich series, faucet auth
https://www.pinestake.com/apiWebsite Next.js routes — epoch calendar history, feature gates, inflation, MEV helpers

Most endpoints are unauthenticated GET and return JSON. Faucet / session routes require a GitHub OAuth cookie (see Faucet).

Calendar & epoch data

Historical epoch wall-clock times (similar in spirit to Stakewiz all_epochs_history) live under the website API — start with GET /api/epoch/history.

Conventions​

  • Lamports — on-chain SOL amounts are usually integers in lamports (1 SOL = 1e9 lamports), unless a field name says otherwise (totalStake, solStaking, …).
  • Commission — newer payloads prefer basis points (commission_bps, or commission: 500 = 5%). Older list fields may still use percent integers.
  • Caching — several website routes set Cache-Control / ISR; core API responses are refreshed on a backend schedule (lastSyncedAt when present).

Sections​