Skip to content
Tutorials/Widgets and integrationsIntermediate8 min read

Prepare ball tracking and live connections

Understand account activation, outbound IP approval, server-side relays and the distinction between ball tracking, commentary, heatmaps and live odds.

Flow / One controlled server connection, your own delivery
  1. Step 1: Activation

    Confirm the exact service

  2. Step 2: Server egress

    Approve required outbound IPs

  3. Step 3: Relay

    Authenticated server collection

  4. Step 4: Visitors

    Your own saved or relayed data

Identify the service you actually need

Live scores, text commentary, ball coordinates, player heatmaps and live betting odds are different data families. Working score access does not prove a populated coordinate stream, and a heatmap does not prove continuous possession tracking.

Review the service's documentation and confirm account activation, credentials and any server-IP requirements. Do not assume a standard REST key unlocks every specialised connection or that a demonstration animation is real live data.

Confirm the connection model and any required server IPs

For FootballAPI.net's managed relay, your website connects to our delivery endpoints rather than the upstream service. Do not assume every browser visitor or client website needs upstream IP approval. If your account has a separately arranged direct specialist connection, support will confirm whether your server's public outbound IP must be approved.

A website domain, an inbound hosting address and a proxy credential URL are not the same as an outbound IP address. For any direct static-egress arrangement, keep proxy credentials secret and verify the real egress addresses. Do not change ordinary REST integration settings merely because a separate live connection has an IP requirement.

Keep authentication and reconnection on your server

Use one controlled collector or relay for the permitted audience, coordinate reconnects and preserve event timestamps. Keep credentials and connection URLs out of browser code. Handle connection close, timeout and temporary throttling with bounded backoff.

Publish only the data your account is entitled to deliver and avoid forwarding arbitrary connection headers from a customer's browser. A stable relay should prevent one browser refresh from spawning another unmanaged upstream session.

Render only verified live fields

A native DIV-based tracker can display the visual state without an iframe and can support configured sponsor logos. Use actual supplied coordinates and event descriptions for live mode, and clearly distinguish demonstration playback from real tracking.

Do not invent the player in possession, a corner, a throw-in or a free kick when the actual record does not contain it. Optional data and event semantics need to be qualified with a populated sample before a customer-facing promise is made.

Validate the activation before promising coverage

Use a known currently covered fixture and confirm meaningful payload content, timestamps and reconnect behaviour. An open socket, token response or HTTP 200 envelope is not by itself a working ball tracker.

Ask support to verify account-specific access if the connection is rejected or empty. An IP approval issue, wrong registered credential and unavailable fixture are different diagnoses; repeatedly reconnecting cannot resolve all three.

All 51 tutorials