Tutorial · 8 min · endpoints verified 2026-09-22

How to build a WNBA schedule browser

Browse the loaded 2026 WNBA season with explicit date and status filters. This guide uses only the routes currently supported for WNBA; it never fills a gap with NBA data.

API coverage and endpoint overview: Explore the WNBA API

Why this is hard

The data contract behind a WNBA schedule browser

A schedule browser needs stable chronology and honest season scope; silently accepting an older-season selector would imply history that is not loaded.

  • Only the 2026 WNBA season is advertised.
  • Use UTC kickoff values for sorting and localize only at display time.
  • Preserve canonical match and team IDs instead of joining on display names.
  • Show source timestamps and a useful empty state when a query returns no rows.

Path 1 · recommended

Have your AI agent build it

Use MCP for discovery, then make the workflow-specific REST request when the MCP tool set does not expose that enrichment.

1. Connect the MCP server

Add the server in your MCP client and sign in with your Big Balls account. Your client registers itself and handles the token exchange — there is no key to copy.

MCP client configjson
{
  "mcpServers": {
    "bigballs-sports-data": {
      "url": "https://mcp.bigballsdata.com/mcp"
    }
  }
}

2. Tools your agent gets

  • get_matches

    Live, upcoming or historical matches for a sport or league.

  • get_coverage

    Machine-readable map of what we hold and what we do not.

3. Ask for what you want

Paste this at your agent. It is written to make the model check coverage before it designs anything, which is what stops it inventing a field we do not serve.

Prompttext
Build a WNBA schedule browser. Start with get_coverage for basketball, then get_matches with league=wnba. Preserve canonical IDs and timestamps. Use only WNBA capabilities documented by Big Balls Sports Data. If a field is unavailable, show that state and do not substitute an NBA value.

What the agent cannot reach

The MCP server does not expose every REST route used below. It also cannot make an unsupported WNBA field appear, so keep the REST capability boundary visible in the final interface.

Path 2 · hand-coded

Build it yourself

The sequence below starts from a league-filtered collection, follows a returned ID, and shapes only fields the response actually carries.

  1. 01

    List the WNBA population

    Begin with an explicit sport and league filter. Check HTTP status before interpreting an empty data array.

    League-scoped requestbash
    curl -s "https://api.bigballsdata.com/v1/matches?sport=basketball&league=wnba&season=2026" \
+  -H "x-api-key: $BBS_API_KEY"
  2. 02

    Follow the canonical identifier

    Keep the canonical IDs from every list row; they are the stable links to later detail and team-history calls.

    Inspect the collectionbash
    curl -s "https://api.bigballsdata.com/v1/matches?sport=basketball&league=wnba&season=2026" \
+  -H "x-api-key: $BBS_API_KEY" | jq '.data[0]'
  3. 03

    Create the product view model

    Transform the served fields without inferring unavailable metrics. The example keeps null and empty states explicit.

    Honest view modeltypescript
    const schedule = games
  .map((game) => ({ id: game.id, tipoff: game.kickoff_utc, home: game.home.name, away: game.away.name, status: game.status }))
  .sort((a, b) => Date.parse(a.tipoff) - Date.parse(b.tipoff));

Reference

Every endpoint this tutorial uses

All on the gateway at api.bigballsdata.com. Verified against production on 2026-09-22.

MethodPathReturnsWhy you need itPlan
GET/v1/matches?sport=basketball&league=wnba&season=2026League-scoped games, teams, status and scoresDefines the exact game population and supplies canonical identifiers.Free

Pricing, honestly

The current schedule starts on Free

Use the loaded 2026 season as the declared population. Do not sell an upgrade as access to WNBA seasons the API does not hold.

Free key

jsonjson
The served 2026 schedule and results.

Solo

jsonjson
Higher volume and separately verified paid routes.
  • Cache completed games instead of polling immutable rows.
  • Treat plan_required as a product boundary, not a retryable outage.
  • Keep the WNBA capability set separate from NBA.
See the full plan ladder →

More tutorials

Other build guides

Known gaps

What this workflow deliberately leaves out

A useful first version is narrower than a misleading one. Add another panel only when its league-specific route and fields are verified.

  • Only the 2026 WNBA season is advertised.
  • Use UTC kickoff values for sorting and localize only at display time.

Questions

Can I replace missing WNBA fields with NBA data?
No. The schemas may be related, but the identities, competitions, and capability depth are not interchangeable.
What should the UI do with an empty response?
Check the status and error envelope, then show a dated empty state. Never turn a failed read into a factual zero.
Where do the plan labels come from?
The route floors come from the endpoint-plan registry used by the product and its checks. A sport-specific floor can override the shared route floor.

Related APIs

Other APIs you can build with:

WNBA APIBasketball API — Every League, One SchemaNBA API — Live Scores, Box Scores & PropsNCAA Basketball API

Also on this sport

NBA Shot Chart APIInjury Data API for Developers: Free

Stats reference

NBA Player Stats APINBA Player Props API

Ship a WNBA schedule browser

Start with the supported WNBA workflow, preserve its evidence, and add depth only when the league really serves it.