Tempus Ex · AsyncAPI Specification

FusionFeed Realtime (GraphQL Subscriptions)

Version v2

Live push of sports data from FusionFeed over WebSocket. Subscriptions use the graphql-ws protocol (legacy subscriptions-transport-ws is also supported). Authentication is provided in the connection-init parameters as {"authorization": "token MY_API_KEY"} because browsers cannot set WebSocket headers.

View Spec View on GitHub CompanySports DataSportsVideoStreamingTelemetryGraphQLRESTMediaNFLAnalyticsAsyncAPIEventsWebSockets

Channels

graphqlSubscriptions
WebSocket channel carrying GraphQL subscription operations (graphql-ws framing). Clients subscribe to live game data such as telemetry packets, automated statistics and scoreboard updates as it is produced during a game.

Messages

GraphQLSubscribeMessage
graphql-ws subscribe
Client registers a GraphQL subscription operation.
GraphQLNextMessage
graphql-ws next
Server pushes the next subscription result.

Servers

wss
production
FusionFeed GraphQL subscriptions WebSocket endpoint.

AsyncAPI Specification

Raw ↑
generated: '2026-07-21'
method: generated
source: https://docs.tempus-ex.com/fusionfeed/graphql/executing-queries
spec_type: AsyncAPI
x-note: >-
  Generated by API Evangelist from the documented FusionFeed GraphQL
  subscription transport. FusionFeed pushes live data (e.g. telemetry, stats,
  scoreboard updates) to clients via GraphQL subscriptions over WebSocket using
  the graphql-ws protocol at /v2/graphql-ws. This AsyncAPI captures that real
  streaming surface; the concrete subscription fields are defined in the
  provider's GraphQL schema, not published as a standalone document.
asyncapi: 3.0.0
info:
  title: FusionFeed Realtime (GraphQL Subscriptions)
  version: v2
  description: >-
    Live push of sports data from FusionFeed over WebSocket. Subscriptions use
    the graphql-ws protocol (legacy subscriptions-transport-ws is also
    supported). Authentication is provided in the connection-init parameters as
    {"authorization": "token MY_API_KEY"} because browsers cannot set WebSocket
    headers.
  externalDocs:
    url: https://docs.tempus-ex.com/fusionfeed/graphql/executing-queries
servers:
  production:
    host: feed.fusion.tempus-ex.com
    pathname: /v2/graphql-ws
    protocol: wss
    protocolVersion: graphql-ws
    description: FusionFeed GraphQL subscriptions WebSocket endpoint.
    security:
    - $ref: '#/components/securitySchemes/connectionInitToken'
channels:
  graphqlSubscriptions:
    address: /v2/graphql-ws
    description: >-
      WebSocket channel carrying GraphQL subscription operations (graphql-ws
      framing). Clients subscribe to live game data such as telemetry packets,
      automated statistics and scoreboard updates as it is produced during a
      game.
    messages:
      subscribe:
        $ref: '#/components/messages/GraphQLSubscribeMessage'
      next:
        $ref: '#/components/messages/GraphQLNextMessage'
operations:
  receiveGameUpdates:
    action: receive
    channel:
      $ref: '#/channels/graphqlSubscriptions'
    summary: Receive live GraphQL subscription payloads pushed by FusionFeed.
    messages:
    - $ref: '#/channels/graphqlSubscriptions/messages/next'
components:
  securitySchemes:
    connectionInitToken:
      type: userPassword
      description: >-
        API key passed via the graphql-ws connection-init parameters as
        {"authorization": "token MY_API_KEY"}.
  messages:
    GraphQLSubscribeMessage:
      name: subscribe
      title: graphql-ws subscribe
      summary: Client registers a GraphQL subscription operation.
      contentType: application/json
      payload:
        type: object
        properties:
          id: { type: string }
          type: { type: string, const: subscribe }
          payload:
            type: object
            properties:
              query: { type: string, description: GraphQL subscription document }
              variables: { type: object }
              operationName: { type: string }
    GraphQLNextMessage:
      name: next
      title: graphql-ws next
      summary: Server pushes the next subscription result.
      contentType: application/json
      payload:
        type: object
        properties:
          id: { type: string }
          type: { type: string, const: next }
          payload:
            type: object
            properties:
              data: { type: object }
              errors: { type: array, items: { type: object } }

Work with this as data

Every AsyncAPI spec here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for asyncapi

4 MCP tools reach this
  • find_asyncapisBrowse and filter every AsyncAPI spec in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This AsyncAPI spec
curl "https://apis.io/api/v1/asyncapis/tempus-ex-fusionfeed-asyncapi"
All asyncapi
curl "https://apis.io/api/v1/asyncapis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.