Update for Bitfinex V2 API Endpoints

We’re updating the FIRST_TRADE field across several Bitfinex V2 API endpoints and channels. These changes took effect on 23 September 2026.

What is FIRST_TRADE ? 

FIRST_TRADE represents the timestamp of the very first trade executed on a given trading pair and can be either int or null:

• int (Timestamp): Returned when a trading pair has an existing trade history.
• null: Returned when a pair is newly listed and has no executed trades yet.

If your integration uses any of the below endpoints or channels below, please review these changes and update your implementation as soon as possible.

What’s changing

The FIRST_TRADE field is being updated across the following V2 API endpoints and WebSocket channels:

• pub:info:pair
• pub:info:pair:bitfinex
• pub:info:pair:futures
• pub:info:pair:futures:bitfinex
  The first element will now return FIRST_TRADE as int | null
  Check documentation
• /v2/ticker/
  FIRST_TRADE will now return int | null
  Check documentation
• /v2/tickers
  FIRST_TRADE will now return int | null
  Check documentation
• WebSocket ticker channel: { event: 'subscribe', channel: 'ticker', symbol: }
  FIRST_TRADE will now return int | null
  Check documentation

What you need to do

If your integration uses any of the endpoints or channels above, please review your implementation as soon as possible and make sure it can handle FIRST_TRADE returning either an integer (int) or null.