Basketball Scores API | NBA, EuroLeague Live & Results

Basketball games including NBA, EuroLeague and national leagues: every game today, live now, any date window, or the results and fixtures of named teams or competitions. Quarter scores, team records and the moneyline on every row. A Sofascore and Flashscore alternative that runs on Apify without proxies. Charged per game returned.

$0.002 per basketball match, plus $0.005 once per run. Anything that fails, is not found, or returns nothing is skipped and not charged.

What data does this actor return?

One MatchRow per result, exported as JSON, CSV or Excel, or read from the Apify API:

competition, home_team, home_record, home_score, away_score, away_record, away_team, status, winner, odds_home, odds_away, start_time, event_id, url

Timestamps are ISO 8601 in the timezone you choose, and field names are identical across all nine actors in the suite. Every row carries the source's own ids, so results chain straight into the other actors without a second lookup.

How to use it

1. Open the input tab and pick a mode.
2. Type names, not ids. "Premier League" and "Carlos Alcaraz" are resolved through the source's own search, so you never have to look a number up.
3. Set Max matches to bound the run. Results are ordered by importance first, so a small cap returns the biggest matches rather than an arbitrary slice.
4. Press Start. A typical run finishes in two to five seconds.
5. Export as JSON, CSV or Excel, or call the dataset from the Apify API.

Example output

{
  "competition": "NBA",
  "home_team": "Los Angeles Lakers",
  "home_record": "9-3",
  "away_team": "Denver Nuggets",
  "away_record": "8-4",
  "home_score": 112,
  "away_score": 106,
  "status": "Ended",
  "winner": "home",
  "event_id": 4487551
}

How much does it cost to get basketball scores?

Run	Cost
1 basketball match	$0.007
100 basketball matches	$0.205
1,000 basketball matches	$2.005

You are charged per basketball match delivered, plus one run fee. There is no subscription and no minimum. The run fee exists so a run that returns a single row still covers its own compute.

Uses

• NBA and EuroLeague result feeds
• Quarter-by-quarter scoring history for a team
• Feeding game ids into the odds and box-score actors

Honest billing

This actor charges only for what it delivers. A match that is not found, a name that does not resolve, a market that is not published, or a request the source refuses is logged and skipped at no cost. Every run writes a RUN_SUMMARY record to its key-value store stating exactly how many rows were charged and how many were skipped, so you can audit any bill.

The rest of the suite

All of these share one client and one set of field names, so ids and rows chain between them:

Actor	What it does
live-scores-api	Every match live right now across football, tennis, basketball and six more sports, one row per match with score, minute, period scores and main-line odds. No proxy, no key. Charged per live match.
tennis-scores-api	Tennis matches today, live, by date, or per player and tournament: set scores with tiebreaks, live point, ATP/WTA ranking, tour and match-winner odds on every row. No proxy needed. Charged per match.
football-scores-api	Football matches today, live, by date, or per club and competition: half-time and full-time scores, minute, round, venue and the 1X2 line on every row. No proxy needed. Charged per match.
sports-odds-api	Bookmaker odds per match: main market plus promoted markets and player props, decimal/fractional/American, opening price and movement. Price ids or a whole day of a sport. Charged per match.
match-stats-lineups-api	Full match data: team stats (possession, xG, shots), both lineups with ratings and per-player stats, goals, cards, subs, H2H, venue and referee. Ids or a team's latest match. Charged per match.
league-standings-api	League tables for any competition in nine sports: position, played, W/D/L, goals, points, form, streak, zones, plus pct and games behind for NBA-style tables. Charged per table.
sports-search-api	Resolve team, player and competition names to ids across nine sports, with sport, country, club and URL. The glue for the other actors in this suite. Charged per query with results.

FAQ

Do I need an API key or a proxy?

No. The source serves Apify's own IP ranges directly, so this actor runs on the free plan with no proxy and nothing added to your bill for proxy traffic. There is no login, no API key and no rate-limit token to manage. Leave the proxy input empty unless you hit limits at high volume.

Where does the data come from?

From 365Scores' public JSON API, the same endpoint their own website reads. It is not an official partner API, so it can change without notice. Every route is tested against captured payloads on each build, and the first response per route is logged so an upstream change shows up immediately in the run log.

How often can I run it?

As often as you like. Use Apify's scheduler for a recurring pull, for example every minute for live scores or once a night for results. Each run is billed independently at the prices above, so a schedule costs the per-run fee each time it fires plus whatever it delivers.

What happens if a name cannot be resolved?

It is logged as a warning, skipped, and not charged. The run continues with the names that did resolve, so one bad spelling in a list of fifty does not fail the run. Use the search actor first if you want to confirm ids before a large run.

Can I use the ids in the other actors?

Yes, that is the point of the suite. Every row carries event_id, and team, player and competition ids where they apply. Paste them straight into the odds, match stats or player stats actors. No id translation is needed because all nine read the same source.

Source and reliability

Data comes from 365Scores' public JSON API, the same one their website reads. No key, no login, and unlike Sofascore or ESPN it serves Apify's own IP ranges directly, so no proxy is needed. Every route was verified against live responses, the parsers are tested against captured payloads on every build, and the first response per route is logged in a [shape] line on each run so an upstream change is visible immediately. If a route ever fails, the raw response is saved to the run's key-value store as DIAG_<route> for diagnosis.