Integration Scenarios
Each scenario page walks one integration goal end to end: the feeds involved, the workflow, request and response samples, and best practices. Every page stands alone; start with the one that matches your goal.
Scenarios
| Scenario | Build this when you need |
|---|---|
| Schedules | Season, daily, and historical schedules; game statuses and coverage flags |
| Live Game Updates | Live scores, full boxscores, and event-level play-by-play with shot locations |
| Standings and Rankings | Conference and division tables, record splits, seeds, and clinch markers |
| Rosters and Player Statuses | Team rosters, player profiles and statistics, leaders, free agents, and transfers |
| Playoffs and Tournaments | The playoff bracket as linked series, series statistics, and the Showcase Cup |
| Monitoring Data Changes | Change detection that keeps a local store current without re-crawling |
Where to Start
| If you are building | Start with | Then add |
|---|---|---|
| A scores app or widget | Schedules | Live Game Updates, Standings and Rankings |
| A stats or fantasy product | Rosters and Player Statuses | Live Game Updates, Monitoring Data Changes |
| A standings and playoff tracker | Standings and Rankings | Playoffs and Tournaments |
| A data warehouse or sync layer | Schedules | Monitoring Data Changes, Rosters and Player Statuses |
| A results archive or backfill | Historical Data | Schedules |
Before You Build
- Read G League API Basics for authentication and the URL shape, and G League Fundamentals for the season-type model (
SC,SCC,REG,PST); season types appear in almost every feed path - Read ID Handling before designing storage: GUIDs are the primary keys, and
referencevalues bridge to official league identifiers - Check the Update Frequencies chart before choosing polling cadences
- Skim Game Status Workflow: every polling loop keys on the status lifecycle
Updated about 14 hours ago
Did this page help you?
