exchange_listing_events. The legacy exchange_listings aggregate remains available for backward-compatible recent and hub payloads while new event APIs expose the richer lifecycle model.
Listing events
GET /v1/listings/events
Returns the canonical event feed used by the listings feed and calendar views. Supports CEX Spot markets, derivatives markets, and Perp DEX venues.
Query parameters
Filter to a single venue, for example
binance, okx, bitget, bybit, or aster. A venue with no enabled connector sets partial: true with a reason in partial_reasons; GET /v1/listings/exchanges shows which venues and market types are enabled.Opaque cursor returned as
next_cursor. Pass it through unchanged; it advances database and official-overlay rows independently.cURL
Response shape
generated_at is when the API assembled the response; do not use it as market-data freshness. Use last_updated_at for the freshest real row observation and inspect partial, partial_reasons, and provider_coverage before acting on an apparently quiet feed.
partial is true exactly when partial_reasons is non-empty. Each reason is one sentence naming the gap:
- a provider whose request failed;
- a live exchange instrument feed whose newest listing is more than 60 days old;
- the hourly spot-listings ingest, when the query covers its venues and its last completed run is more than 2 hours old (or no completed run is logged);
- the canonical events table being unavailable, in which case rows come from the compatibility table and
sourceiscompatibility; - a requested
exchange,venue_type, ormarket_typethat no enabled connector covers, so an empty or short result is not evidence that nothing was listed.
status: "error" in provider_coverage; the rows that did arrive are still usable.
Exchange coverage
GET /v1/listings/exchanges
Returns the typed connector registry: supported market types, source URLs, parser confidence, enabled status, and polling group for each exchange.
Query parameters
cURL
Hub payload
GET /v1/listings/data
Returns the full New Listings hub payload: weekly and monthly aggregated counts by narrative and by exchange, recent listings for the last 90 days, and summary stats. This is the same data that powers the /new-listings terminal page.
Query parameters
Filter to a single narrative slug (e.g.
ai-agents, memes, layer-1, rwa, defi). When set, all returned counts are scoped to that narrative.Filter to a single exchange. Legacy aggregates currently contain enabled compatibility venues; event APIs expose the full registry.
Response fields
Weekly buckets, last 26 weeks. Each element:
{ bucket_date, exchange, narrative_slug, listing_count }. bucket_date is ISO-week Monday (UTC).Raw rows from the last 90 days, newest first. Each:
{ id, token_symbol, token_name, token_coingecko_id, exchange, listing_date, listing_date_source, narrative_slug }.Top 5 narratives ranked by listing count in the current month. Each:
{ narrative_slug, count }.Response (truncated)
Recent listings feed
GET /v1/listings/recent
A flat list of recent token listings. Defaults remain compatible with the legacy spot feed. The legacy feed holds only resolved spot listings (a CoinGecko id and a mapped narrative), so brand-new tokens awaiting resolution and perps are missing, and it returns no next_cursor: limit truncates it. Event-specific filters such as market_type, event_type, status, and confidence, a from/to/cursor, or an exchange outside binance, okx, bybit, gateio and mexc switch the endpoint to the canonical event feed (spot and perp, every status, cursor-paged) while preserving the old row shape.
Query parameters
Filter to a single exchange, including enabled compatibility venues and event-registry venues such as
bitget, bingx, or aster.Optional event-feed instrument filter:
token, spot_pair, perp_contract, futures_contract, or options_contract.Optional event-feed status filter:
announced, scheduled, live, completed, cancelled, or needs_review.Response fields
Array of listing rows sorted by
listing_date descending. Each: { token_symbol, token_name, token_id, exchange, listing_date, listing_date_source, narrative_slug }.Freshest real source observation on event-feed responses. Do not substitute
generated_at.Present on event-feed responses. One sentence per coverage gap (a failed or stale provider, or a requested venue or market type with no enabled connector), as described under listing events. Empty when coverage is whole.
Source values
Legacy rows carrylisting_date_source; canonical event rows carry source_kind and source_confidence:
exchange_kline: derived from the exchange’s own k-line first-trade timestamp (authoritative)official_api/official_status: parsed from an exchange or perp DEX public endpointofficial_announcement: parsed from an exchange announcement sourcemarket_data: inferred from market data when no announcement source existsproxy/first_seen: when Sharpe first observed the instrumentmanual: admin-set
Response (truncated)
Narratives
Every listing is tagged to one of Sharpe’s 30 canonical narrative slugs (same taxonomy as/v1/narratives/data). The hub (/v1/listings/data) and the default recent feed count only rows with status = 'active' and a resolved narrative, so they undercount the newest listings. The event feed (/v1/listings/events) also returns unresolved listings as status = needs_review, usually with narrative uncategorized.
Supported narrative slugs
layer-1 · layer-2 · defi · ai-agents · defai · depin · desci · gaming · dex-tokens · cex-tokens · lending · memes · nfts · oracles · privacy · rwa · stablecoins · restaking · liquid-staking · modular · socialfi · intent · prediction-markets · perps · bridges · account-abstraction · tap-to-earn · telegram-apps · zk · yield-farming
Update cadence
Listing announcements are not high-frequency market data, but launch workflows benefit from tighter freshness. Enabled connectors run hourly in grouped cron windows, and the rollup cron follows after ingestion to refresh compatibility and event-derived materialized views.
The core ingest runs every enabled snapshot connector. Venues in the registry’s extended group have no enabled connector, so no ingest runs for them; their listings come only from an official overlay where the venue has one. Disabled connectors stay out of cron until fixture parsing and rate-limit behavior pass validation.

