Get a cricket player's career debut and last-played details per format by playerId, with opponent, date, venue and match IDs

View all Cricket Live Scores, Scorecards & Stats API endpoints →

Returns a player's career milestones by competition format. The only input is playerId, a required number sent in the URL path (the default 8733 is the documented example value). The source 200 example is an object with an appIndex object (seoTitle and webURL strings) and a values array with one entry per format. Each entry has a name (t20, test, odi, ipl and cl in the example), a debut string, a lastPlayed string and, for formats the player has appeared in, debutMatchID and lastPlayedMatchId as numeric strings. The debut and lastPlayed strings are free text in the pattern opponent, date (YYYY-MM-DD) and venue, for example a line that starts with vs followed by a team name; the example contains a doubled space after the first comma. For a format the player never appeared in, the example shows the text Not played in both debut and lastPlayed and omits the two match ID fields. The entries are not sorted in a documented order, and the spelling of the two match ID keys differs (debutMatchID and lastPlayedMatchId), so read each key exactly as returned. No live probe was recorded for this endpoint, so every response field described here comes from the source example and is not independently verified. This operation gives debut and last-played markers, not a per-match history or career totals.

API Features

One entry per format The values array holds a separate object for each format name (t20, test, odi, ipl and cl in the source example), so a career summary needs one request and no merging of per-format calls.
Debut line with opponent and venue The debut string combines the opponent, an ISO-style date and the ground, which gives a ready-made caption for a first-appearance timeline without a second lookup.
Last-played marker lastPlayed uses the same opponent, date and venue pattern, so a client can show when a player was most recently selected in each format and judge how current the record is.
Match IDs for follow-up lookups debutMatchID and lastPlayedMatchId are numeric strings that identify the matches themselves, which lets a page link a debut or final appearance to match-level data.
Explicit Not played marker A format the player never appeared in carries the text Not played in debut and lastPlayed and has no match ID fields, so an absent format is distinguishable from missing data.
Single-parameter request Only playerId is needed, with no series, format or paging inputs to configure, so the career block is easy to cache against one player key.
Career summary apart from stat tables This operation returns dated career markers only, so it complements the batting and bowling tables on a profile page and does not repeat their statistics.

Live API Demo

GET /api/project/cricbuzz-cricket/players-get-career

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-get-career?key=<API_KEY>&playerId=8733'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

What does the player career operation return?

It returns an appIndex object and a values array with one object per format. Each object has name, debut and lastPlayed, plus debutMatchID and lastPlayedMatchId when the player has appeared in that format, according to the source 200 example. No live probe was recorded, so these fields are not independently verified.

What is the only input?

playerId, a required number in the URL path; the default is 8733. Get it from the id field of the trending players or player search operations. There are no format, series or paging parameters, so every format is returned in the same response.

What do the debut and lastPlayed strings contain?

They are free text that combines the opponent, a date written as YYYY-MM-DD and the venue, separated by commas, as in the source example. The example contains a doubled space after the first comma, so trim whitespace before displaying or splitting the string.

What does Not played mean?

For a format the player never appeared in, the example shows the text Not played in both debut and lastPlayed and leaves out the debutMatchID and lastPlayedMatchId fields. Check for that text and for missing keys before you build a link or parse a date.

Are the match IDs usable with other operations?

They identify the debut and last-played matches as numeric strings. You can pass them to the match-level operations of this product, but coverage depends on the data source, so a match page can still come back empty for an older fixture.

Why do the match ID keys look inconsistent?

The source example spells them debutMatchID and lastPlayedMatchId, with different capitalization of Id. Read each key exactly as written and do not rely on a case-insensitive match in strict clients.

Does the response include career totals or a match-by-match history?

No. The documented fields are debut and last-played markers per format only. Use the batting and bowling statistics operations for figures, and do not present this response as a complete event log.

Is the order of the format entries fixed?

It is not documented as fixed. The example lists t20 before test and odi, so key the entries by their name field instead of by array position.

Related operations

Guides

View Subscription Plans →