Integrate the newer scores snapshot
Use the newer scores endpoint as a server-side snapshot, validate match IDs and dates, and avoid duplicate collectors for the same scoreboard.
Endpoint reference:scores-newStep 1: Identify
No required query parameters; check your plan access.
Step 2: Request
GET /api/v1/football/scores-new
Step 3: Validate
Check resource IDs, actual dates and available fields.
Step 4: Reuse
Save a shared snapshot; this feed's source cache lasts 30 seconds.
What you will build
Use the newer scores service when its snapshot format suits your integration. Treat it as an alternative score input, not a second source to poll alongside the original feed without a specific reason.
New scores service. Provider-compatible football data; availability varies by competition, date and account entitlement. Starter: restricted to your saved leagues.
Check your plan before starting
This endpoint is included in Starter's league-scoped service set as well as Growth and Pro. Starter customers must save their league choices in Dashboard → Settings first. League-addressed requests must use a saved league; aggregate score responses are filtered to the account's saved leagues.
The service being published does not guarantee every optional field for every competition or fixture. Check the actual records relevant to the page you are building.
Find identifiers and prepare the request
This route has no customer query filters. Retrieve its snapshot, inspect the returned competition identifiers, and apply your own permitted presentation filters to the saved data.
Identifiers are strings belonging to specific resources. Keep competition, stage, team, player and static match IDs in separate fields. The code reads identifiers from your environment rather than assuming one sample league is valid for everyone. Growth and Pro customers can discover IDs in the directory; Starter customers should use their saved league IDs from Dashboard → Settings and their permitted fixture or squad records.
- This endpoint accepts no query parameters. Do not append unsupported filters.
Make an authenticated server-side request
Set FOOTBALLAPI_KEY to your customer REST key in your server's secret manager. No other environment variables are needed for this example. Save the code as request.mjs and run node request.mjs with Node.js 20 or newer. A widget installation key cannot replace the REST key.
The example makes one request and does not retry automatically. Its 60-second client timeout leaves room for the API's bounded source-read recovery; it is not a promised response time or a browser loading recommendation. Test once in the signed-in playground, then run from a server you control. Visitors should request your own cached delivery route.
A successful transport response is the beginning of validation, not proof that every optional record is populated. Preserve the response metadata alongside the data.
// Save as request.mjs and run: node request.mjs (Node.js 20+).
// Set the environment variables listed above first. Run only on your server.
const requiredEnv = name => {
const value = process.env[name]?.trim();
if (!value) throw new Error(`Set ${name} before running this example`);
return value;
};
const key = requiredEnv("FOOTBALLAPI_KEY");
const url = new URL("https://footballapi.net/api/v1/football/scores-new");
const response = await fetch(url, {
headers: { Authorization: `Bearer ${key}`, Accept: "application/json" },
signal: AbortSignal.timeout(60000)
});
if (!response.ok) {
const retryAfter = response.headers.get("retry-after");
throw new Error(`Football API HTTP ${response.status}; Retry-After: ${retryAfter ?? "not supplied"}`);
}
const { data, meta } = await response.json();
console.log({ data, meta });Interpret and render the response
Compare durable static match IDs, dates and supplied statuses before merging this snapshot with fixtures. Response receipt time alone does not establish match-data freshness.
Normalise the received structure into the same internal scoreboard model as your other pages. Retain source timestamps and avoid replacing a known final score with an older scheduled record.
Responses use a data object and meta information. Feed-native fields may use @ prefixes, and repeated elements can be an object or an array. The helper below is an adapter utility, not a standalone renderer: apply it to the specific collection shown in the reference. Preserve missing values instead of turning unavailable statistics into zero.
const asArray = value => value == null ? [] : Array.isArray(value) ? value : [value];
// Adapter helper: apply to the known collection from this endpoint's reference.
// It does not guess a response path or render a complete page.
// Keep static match IDs and player/team IDs in your saved normalised records.Save requests without losing useful updates
Collect one snapshot and fan it out through your own server. The published reuse interval is longer than the original scores endpoint; do not assume that polling faster produces fresher records.
The published server cache interval for this endpoint is 30 seconds. This is a server reuse interval, not a guarantee of new data every 30 seconds and not a promise that requests served from the API cache are free. Your own cache prevents repeat customer API requests.
Include the endpoint, sorted query parameters, account access scope and relevant date or season in your cache key. Coalesce concurrent misses, serve your own saved response while one background refresh runs, and record its fetched time. Apply corrections to stored results without discarding stable IDs.
Date and time fields are retained as supplied. Establish the timezone for the particular feed before converting a kickoff to UTC or a visitor's local time; do not append Z to a timezone-less value just to make it parse.
Check the result before going live
If you already operate a collector using scores, measure whether this alternative adds a necessary field before enabling another permanent polling job.
A 400 response usually needs an input correction, 401 needs a valid key, and 403 needs a plan, saved-league or access check. A disabled endpoint can return 503. Honour Retry-After on 429 responses rather than retrying immediately. Back off on temporary 5xx errors. An empty successful collection is not a reason to launch an unbounded retry loop.
- Use a known relevant fixture or player for your first comparison.
- Check that returned competition, season and dates match the page you are building.
- Keep keys and raw authentication headers out of error logs and support screenshots.
Related tutorials
Endpoint tutorials / 6 min
Build a scoreboard with scores and results
Fetch today's football scores, interpret match states and minutes, join static match IDs and share a five-second scoreboard cache across visitors.
Build a football product / 11 min
Build a fast football match centre
Combine fixtures, live states, summary events, statistics, formations, images and odds into one preloaded football match-centre model.
Getting started / 9 min
Make your first FootballAPI.net request
Create an account, activate the right football plan, keep your API key server-side and make a first authenticated scores request with cURL or PHP.
Performance and operations / 12 min
Save requests with shared football API caches
Design server-side caching, request coalescing, prewarming and usage budgets so football pages load quickly without unnecessary API calls.