Discover/MSport API
live

MSport APImsport.com

Access real-time betting odds from MSport Nigeria via 3 endpoints. List sports, fetch matches with main market odds, and retrieve all markets for any match.

This API takes change requests — .
Endpoint health
verified 3d ago
get_matches
list_sports
get_match_odds
3/3 passing latest checkself-healing
Endpoints
3
Updated
1mo ago

What is the MSport API?

The MSport Nigeria API gives developers access to betting odds data across all sports on msport.com/ng through 3 endpoints. The get_matches endpoint returns matches grouped by tournament with main market odds including 1x2, Over/Under, and more. The get_match_odds endpoint exposes full market depth — Double Chance, GG/NG, DNB, and other bet types — alongside outcome probabilities, team names, and match status for any event ID.

Try it

No input parameters required.

api.parse.bot/scraper/ed788d1a-1d1c-4a3a-aa56-1658f52cbd71/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/ed788d1a-1d1c-4a3a-aa56-1658f52cbd71/list_sports' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

Typed, relational, agent-ready

A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.

  • Fully typed · autocompletes
  • Objects link to objects
  • Typed errors & pagination

Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:

uv add parse-sdk
uv run parse init
uv run parse add --marketplace msport-com-api

uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.

"""Walkthrough: MSport Nigeria Odds SDK — bounded, re-runnable; every call capped."""
from parse_apis.msport_nigeria_odds_api import MSport, SportId, MatchNotFound

client = MSport()

# List available sports with match counts
for sport in client.sports.list(limit=5):
    print(sport.sport_name, sport.match_count)

# Search upcoming soccer matches (default sport_id)
match = client.matches.search(sport_id=SportId.SR_SPORT_1, limit=1).first()
if match:
    print(match.home_team, "vs", match.away_team, match.start_time)

    # Drill into full market detail via refresh
    detail = match.refresh()
    print(detail.markets_count, "markets available")
    for mkt in detail.markets[:3]:
        print(mkt.name, [(o.description, o.odds, o.probability) for o in mkt.outcomes])

# Typed error handling on a direct lookup
try:
    odds = client.matches.get(event_id="sr:match:99999999")
    print(odds.home_team, odds.away_team)
except MatchNotFound as exc:
    print(f"Match not found: {exc.event_id}")

print("exercised: sports.list / matches.search / match.refresh / matches.get")
All endpoints · 3 totalmissing one? ·

List all available sports on MSport Nigeria with their current match counts. Each sport includes a sport_id usable as input to get_matches. The count reflects matches currently listed for pre-match betting.

Input

No input parameters required.

Response
{
  "type": "object",
  "fields": {
    "total": "integer, number of sports returned",
    "sports": "array of sport objects each with sport_id, sport_name, match_count"
  },
  "sample": {
    "data": {
      "total": 21,
      "sports": [
        {
          "sport_id": "sr:sport:1",
          "sport_name": "Soccer",
          "match_count": 608
        },
        {
          "sport_id": "sr:sport:2",
          "sport_name": "Basketball",
          "match_count": 64
        }
      ]
    },
    "status": "success"
  }
}

About the MSport API

Sports and Match Discovery

The list_sports endpoint returns every sport currently active on MSport Nigeria, including each sport's sport_id, sport_name, and match_count. The sport_id values (e.g. sr:sport:1 for Soccer, sr:sport:2 for Basketball) are the inputs needed by get_matches. The total field confirms how many sports are available at the time of the call.

Match Listings with Main Market Odds

Passing a sport_id to get_matches returns all upcoming matches for that sport, grouped by tournament. You can narrow results with the optional date parameter (format: YYYY-MM-DD). Each match object includes team names, start times, and main market odds — typically 1x2 and Over/Under lines. The response total field indicates how many matches are returned.

Full Market Depth per Match

The get_match_odds endpoint accepts an event_id string (e.g. sr:match:71766878, obtainable from get_matches) and returns all available betting markets for that specific match. Response fields include home_team, away_team, start_time (Unix timestamp in milliseconds), status (0 = not started, 1 = live), score, sport, category, and a markets array. Each market object lists individual outcomes with their associated probabilities. Markets vary by event but can include 1x2, Over/Under, Double Chance, GG/NG, and DNB.

Reliability & maintenanceVerified

The MSport API is a managed, monitored endpoint for msport.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when msport.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.

This isn't an official msport.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.

Last verified
3d ago
Latest check
3/3 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Build a pre-match odds comparison tool using 1x2 and Over/Under data from get_matches
  • Track live match status and in-play scores via the status and score fields in get_match_odds
  • Aggregate market counts per sport using match_count from list_sports for a sports activity dashboard
  • Filter today's football matches using get_matches with a date parameter and sr:sport:1
  • Calculate implied probabilities from outcome probability data returned by get_match_odds
  • Alert users when specific bet markets (e.g. Double Chance or DNB) become available for a match
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min

One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.

Frequently asked questions
Does MSport have an official developer API?+
MSport does not publish a public developer API or documentation for third-party access to its odds data.
What does `get_match_odds` return beyond the main odds lines?+
get_match_odds returns the full markets array for a match, which can include 1x2, Over/Under, Double Chance, GG/NG (both teams to score), and DNB (Draw No Bet). Each market entry includes its outcomes and their probabilities. It also returns match metadata: home_team, away_team, start_time (millisecond Unix timestamp), current score, status, sport, and category.
Are historical match results or past odds covered?+
Not currently. The API covers upcoming and live matches — get_matches returns upcoming fixtures and get_match_odds includes live status via the status field. Historical results and past odds lines are not exposed. You can fork this API on Parse and revise it to add an endpoint targeting historical match data.
Can I retrieve odds for a specific league or tournament directly?+
Not directly. The get_matches endpoint filters by sport_id and optionally date, but does not accept a league or tournament parameter. Matches are returned grouped by tournament within the response, so tournament filtering would need to be applied client-side. You can fork this API on Parse and revise it to add a tournament-level filter endpoint.
Does the API cover sports other than football on MSport Nigeria?+
Yes. list_sports returns all active sports along with their sport_id values. Basketball uses sr:sport:2, and any other sports listed on MSport Nigeria at query time will appear in the response with their own IDs and match_count values, which you can then pass to get_matches.
Page content last updated . Spec covers 3 endpoints from msport.com.
Related APIs in SportsSee all →
transfermarkt.com API
Search Transfermarkt for football players and retrieve detailed player profiles, transfer histories, market value timelines, performance stats, and club squad/club information.
opendota.com API
Access detailed Dota 2 match statistics, player performance metrics, hero win rates, and professional tournament data to analyze gameplay trends and competitive performance. Search for specific players, explore custom data queries through SQL, and retrieve comprehensive match histories to improve your understanding of the game.
nhl.com API
Access data from nhl.com.
flashscore.com API
Search teams and competitions, pull daily fixtures and live scores, and retrieve match details including events, statistics, and league standings from FlashScore.
racecenter.letour.fr API
Track live Tour de France race updates by accessing real-time rider positions, detailed stage information, and current general classification standings. Monitor how your favorite cyclists are performing throughout each stage and their overall ranking in the competition.
transfermarkt.de API
Access data from transfermarkt.de.
pro-football-reference.com API
Access comprehensive NFL data including season schedules, team standings, player statistics, game boxscores, play-by-play details, and player profiles to research teams, players, and game information. Search for specific players and dive into detailed game analysis with boxscore information and minute-by-minute play data.
fantasypros.com API
Access expert consensus rankings, player projections, average draft position data, injury reports, and the latest player news from FantasyPros. Search by player name or position to retrieve detailed stats, rankings, and expert analysis across all major scoring formats.