Search cricket players by name with plrN and get player IDs, teams, birth dates and face image IDs
View all Cricket Live Scores, Scorecards & Stats API endpoints →Searches for cricket players by name. plrN is the only input and it is required: a player name or name fragment as text, with Tucker as the documented example. The source 200 example is an object with a category string that repeats the search text (Tucker) and a player array. Each player entry has id (a string such as 11131), name, teamName (for example Bermuda, Australia, Ireland, South Africa or Scotland), dob (a date string in YYYY-MM-DD form, or the text N/A when no date is known) and faceImageId (a number). The example lists eight matches for Tucker, several of them people who share a surname but play for different teams, and the same faceImageId 182026 appears on three unrelated entries, so do not treat it as unique per person. The source does not document minimum search length, matching rules, result limits or the no-match response. No live probe was recorded, so all fields come from a source example.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/cricbuzz-cricket/players-search API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/players-search?key=<API_KEY>&plrN=Tucker'
Query Result
Use Cases
- Power a search box that lists each result with name, team and date of birth so the user can confirm the intended player before opening a profile.
- Resolve a player name typed by an editor into an id, then request that player's biography, career, batting or bowling data with the id.
- Match names from a spreadsheet or roster import to ids and flag any name that returns several results for manual review.
- Build a surname explorer that groups search results by teamName, for example for family-name stories or quiz content.
- Seed a player-news or trending-player module by turning a searched name into the id that those endpoints expect, after confirming the parameter type they use.
- Find incomplete records by listing results whose dob is N/A, then queue them for manual enrichment in your own database.
Frequently asked questions
What can I put in plrN?
Use a player name or part of a name. The documented example is Tucker. The source does not describe minimum length, case handling, accents or partial-word matching, so test the inputs your users are likely to type.
Why do I get several players for one search?
The search matches by name, so a surname can return many people. The example for Tucker lists eight entries across Bermuda, Australia, Ireland, South Africa and Scotland. Use teamName and dob to pick the right one, then keep its id.
Which field should I store as the player identifier?
Store id, which is a string in the example, for instance 11131 for Lorcan Tucker. Check the type your downstream player endpoint expects before passing it, because other endpoints may declare player IDs as numbers.
What does dob N/A mean?
In the example, entries such as Fiachra Tucker and Emily Tucker have dob set to the text N/A instead of a date. Treat it as an unknown birth date and do not feed it to a date parser.
Is faceImageId unique for each player?
Not in the example. The value 182026 appears on three different entries, which looks like a shared fallback image. Do not use faceImageId as a person key; use id for that.
What happens when no player matches?
The source does not document a no-match response, and no live probe was recorded. Handle a missing or empty player array, and an empty or 204-style response, as zero results in your client.