API

PumpScan API Reference

PumpScan exposes analytics endpoints used by the web app. They are optimized for recent Pump.fun activity and rolling dashboard windows.

Base paths

The frontend proxies service endpoints under /v1. Several dashboard route handlers also expose /api/v1/* wrappers for no-store browser reads.

Response shapes are designed for the PumpScan application and may evolve with the dashboard.

Endpoint map

EndpointWhat it returns
/v1/eventsPaginated decoded events with filters for signature, mint, bonding curve, creator, user, route program, exact parent program, event type and time window.
/v1/events/:txOne retained decoded transaction payload selected by exact signature.
/v1/metricsCombined daily overview, account, mint and program metrics.
/v1/accountsCreator, trader and active-account rows with sort and wallet filters.
/v1/accounts/:account/rpcCached owner, curve status and 30-second SOL balance hydration. No per-token balance data.
/v1/accounts/:account/accountCached PumpVibe account roles, trade totals, claims and cashback earnings.
/v1/accounts/:account/mintsCached creator/trader mint relations with mint details.
/v1/accounts/:account/relationsRanked co-traders with shared-token counts and first buy/sell position histograms.
/v1/accounts/:account/programsPaginated upstream programs observed for the account, split into routing and execution activity. Transaction-only protocol endpoints are excluded.
/v1/accounts/:account/eventsCompact paginated creator/user transactions for the account.
/v1/accounts/mayhem/accountReserved Mayhem Bot account endpoint; currently returns 501 Not Implemented.
/v1/accounts/mayhem/rpcMayhem Bot on-chain owner, curve status and cached SOL balance hydration.
/v1/accounts/mayhem/eventsRetained event query used only by the Mayhem Bot page.
/v1/tokensToken rankings, launch metadata, flags, reserves, volumes and transaction counts.
/v1/tokens/:token/eventsPaginated events for the mint.
/v1/tokens/:token/mintCached mint metadata and token classification.
/v1/tokens/:token/rpcLive Solana mint-account metadata, authorities, supply and holder counts.
/v1/programsRetained upstream router/integration activity. Terminal protocol and liquidity-venue programs are excluded.
/v1/programs/:program/rpcProgram-owned Solana RPC hydration: getAccountInfo is cached once in the name-anchored program accumulator, getBalance is reused for 30 seconds, and token balances are fetched per request.
/v1/programs/:program/programFilesystem-backed program profile and deployment metadata plus current retained routing and execution activity.
/v1/programs/:program/accountsPaginated accounts observed by the program read model, with routing and execution scopes.
/v1/programs/:program/eventsPaginated cached events from the exact route-program index; this endpoint never traverses the full retained event window.
/v1/topTop account and mint rows for the compact top dashboard.
/v1/overview/trendsTrend insights for peak trade and creation activity, selected-window creates and decoded AMM migration completions.
/v1/overview/chartsSlim chart buckets for buy/sell flow, token categories and unique accounts.
/v1/overview/widgetsWidget buckets for meme coin, mayhem and charity categories.
/v1/resolveAddress-kind resolution for accounts, mints, programs and bonding curves, including bonding-curve-to-mint resolution and optional redirects to dedicated views.
/v1/sol-rateCached SOL/USD rate used for quote normalization and display.
/v1/ws/eventsTopic-based live event WebSocket. Subscribe to events.all or events.mayhem; the Mayhem topic contains exact-wallet Mayhem trades and Pump Mayhem burns.
/v1/ws/metricsTopic-based 3-second snapshot WebSocket. Subscribe to metrics.overview, metrics.mayhem, or both.
/v1/wsCompatibility event WebSocket that starts subscribed to events.all.
/v1/ws/overview/mayhemCompatibility event WebSocket that starts subscribed to events.mayhem.
/v1/ws/overviewCompatibility metrics WebSocket that starts subscribed to metrics.overview and accepts the legacy refresh command.

Window semantics

  • Day endpoints accept day_start_ms and day_end_ms when a caller needs an explicit UTC millisecond window.
  • Overview endpoints accept window_start_ms, window_end_ms, bucket_count and bucket_size_ms.
  • Service time windows use half-open semantics: start is included, end is excluded.
  • Recent event and accumulator retention is capped by the service cache TTL configuration.