[Deprecation Notice] Pyth Pro `/v1/{channel}/streaming` Endpoint — Sunset May 31, 2026

Hi all,

We’re giving advance notice that the TradingView UDF streaming endpoint on the Pyth Pro API Service will be deprecated and removed on May 31, 2026.

What’s being removed

• GET /v1/{channel}/streaming — the Server-Sent Events (SSE) endpoint used to stream real-time price updates in TradingView UDF format.

What’s not changing

The rest of the TradingView UDF surface stays in place. These endpoints remain fully supported:

• GET /v1/{channel}/config
• GET /v1/{channel}/symbols
• GET /v1/{channel}/search
• GET /v1/{channel}/history (OHLC / candles — still the recommended way to fetch chart history)

If you’re using the UDF endpoints to power historical charts, nothing changes for you.

Migration paths

1. If you’re using /streaming to drive live prices in a browser frontend:

Migrate to the Proxy Service HTTP + WebSocket endpoints intended for browser use, with Origin-based auth. See: https://docs.pyth.network/price-feeds/pro/api/proxy

2. If you’re using /streaming from a server or backend:

Migrate to the Pyth Pro WebSocket API, which streams the full real-time feed with token-based auth. See: https://docs.pyth.network/price-feeds/pro/api/websocket

3. If you’re pairing /streaming with a TradingView chart widget (i.e. using the full UDF surface for real-time + history):

The UDF streaming transport specifically will not be publicly supported after May 31. If you need a UDF-compatible real-time feed for a TradingView widget, please reach out. The UDF /history endpoint will continue to work for the chart’s historical bars; only the SSE streaming transport is affected.

We’ll be updating our docs and examples ahead of the sunset with concrete migration snippets for each path.

Timeline

• Now → May 31, 2026 — /v1/{channel}/streaming remains live. Docs and examples will be updated to point to the supported streaming APIs.
• May 31, 2026 — /v1/{channel}/streaming is removed. The other UDF endpoints (/config, /symbols, /search, /history) continue to work as before.

Questions / help migrating

If you’re unsure which streaming API fits your use case, or you need help migrating a production integration, please reply in this thread or reach out in our Telegram / Discord. We’d rather help you move over than have you get surprised at the end of May.

Thanks