Cricket Match vs Scorecard Workflow

Cricket integrations usually work best when match listings and scorecards are treated as different workflow stages, not as interchangeable payloads. This page explains when to use lighter match responses, when to load scorecard detail, and how to connect the two without over-fetching.

curl -s -H "x-api-key: YOUR_API_KEY" "https://novadatahub.com/api/cricket/matches?status=live&limit=5"

import requests
matches = requests.get('https://novadatahub.com/api/cricket/matches', params={'status': 'live', 'limit': 5}, headers={'x-api-key': 'YOUR_API_KEY'}, timeout=60).json()
match_id = matches['matches'][0]['id']
scorecard = requests.get(f'https://novadatahub.com/api/cricket/match/{match_id}/scorecard', headers={'x-api-key': 'YOUR_API_KEY'}, timeout=60).json()
print(match_id, scorecard.keys())

using System.Net.Http.Json;
using System.Text.Json;
using var http = new HttpClient();
http.DefaultRequestHeaders.Add("x-api-key", "YOUR_API_KEY");
var matches = await http.GetFromJsonAsync<JsonElement>("https://novadatahub.com/api/cricket/matches?status=live&limit=5");
var matchId = matches.GetProperty("matches")[0].GetProperty("id").GetString();
var scorecard = await http.GetFromJsonAsync<JsonElement>($"https://novadatahub.com/api/cricket/match/{matchId}/scorecard");
Console.WriteLine(scorecard.ToString());

{
  "ok": true,
  "matches": [
    { "id": "12345", "teams": ["IND", "AUS"], "status": "Live" }
  ],
  "scorecard": {
    "match": { "id": "12345" },
    "innings": [
      { "team": "IND", "runs": 187, "wkts": 4 }
    ]
  }
}