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 backend 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, event type and time window.
/v1/metricsCombined daily overview, account, mint and program metrics.
/v1/accountsCreator, trader and active-account rows with sort and wallet filters.
/v1/mintsMint rankings, launch metadata, flags, reserves, volumes and transaction counts.
/v1/programsRoute-program activity rows with buy/sell counts, lamports and unique traders.
/v1/topTop account and mint rows for the compact top dashboard.
/v1/overview/trendsTrend buckets for total events, buy/sell counts and graduated versus not-graduated event splits.
/v1/overview/chartsSlim chart buckets for buy/sell flow, token categories and unique accounts.
/v1/overview/widgetsWidget buckets for meme coin, mayhem, charity and tokenized-agent categories.
/v1/sol-rateCached SOL/USD rate used for quote normalization and display.

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.
  • Backend time windows use half-open semantics: start is included, end is excluded.
  • Recent event and accumulator retention is capped by the backend Redis TTL configuration.