Fogo Data APIs Are Now Live on Birdeye Data Services

Birdeye Data Services now supports Fogo APIs, giving builders a fast way to pull trading-grade onchain data for dashboards, bots, explorers, analytics, and DeFi apps.

Instead of spinning up and maintaining your own indexing stack, you can plug into BDS and get normalized data through a single interface, so your product logic stays clean even as you scale across chains.

Release date: January 12, 2026

Note: WebSocket support for Fogo is coming soon.

What BDS Supports on Fogo

Fogo apps tend to be latency-sensitive: traders want live updates, bots need reliable triggers, and analytics tools can’t lag behind market moves. With this release, BDS provides the building blocks you need to ship those experiences on Fogo today.

Fogo REST APIs (Available Now)

BDS supports 30+ Fogo endpoints, covering the most-used market and activity data surfaces:

• Price & OHLCV for tokens and pairs (incl. base/quote candles)
• Token overview + metadata
• Trade + market data, including derived metrics such as price change and volume change
• Transactions across multiple views:
  • by token
  • by pair
  • by trader
  • by time range
  • by latest block
• Market lists and ecosystem routing surfaces:
  • trending tokens
  • top traders
  • other ranking lists used for discovery and monitoring

This is enough to power:

• token pages and charting
• “what’s moving” dashboards
• trader leaderboards
• bot logic that reacts to trades / flows
• monitoring and alert systems

Fogo WebSocket Streaming (Coming Soon)

REST coverage gets you live products quickly, but for real-time trading UX and bot triggers, streaming matters.

WebSocket support for Fogo will be released soon, enabling low-latency feeds for live dashboards, alerts, and automated strategies.

Once it’s live, we’ll publish supported subscription types and payload formats in the WebSocket docs.

Why This Matters

If you’re building on a performance chain like Fogo, your product can’t be held back by the data layer.

BDS helps teams:

• ship faster without building custom indexing infra
• keep integrations simple with a chain-agnostic API design
• rely on consistent formats across endpoints (easier analytics + multi-chain expansion)
• scale data consumption as usage ramps up

Start Building on Fogo

1. Get an API key via the BDS dashboard
2. Call REST endpoints with your API key and set the chain to Fogo