Get a cricket image by its image ID, with optional quality (d) and size (p) values.
View all Cricket Live Scores, Scorecards & Stats API endpoints →Request a cricket image by ID. The path parameter imageId is required and is a string: take the numeric image ID supplied by another endpoint, such as a player profile, and add the letter c in front of it. The supplied default is c231889. Two optional query parameters are documented. d accepts high or low, and p specifies the image size as one of de, det, gthumb or thumb. The source text does not explain what each value changes visually, so test the options you plan to use. The path ends in i.jpg, so the request targets a JPEG image resource rather than a JSON document. No response was observed for this operation in the supplied probe evidence, and the only supplied response example is an empty object, so the returned content type, byte size and pixel dimensions for each d and p value are not verified. Keep the image ID as the linking key to the endpoint that supplied it, and confirm that you have the right to publish a given image before using it in a product.
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/images-get-image API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/cricbuzz-cricket/images-get-image?key=<API_KEY>&imageId=c231889'
Query Result
Use Cases
- Resolve an integer image ID supplied by a player profile into an image request, preserving the ID as the linking key.
- Use the endpoint for permitted player or editorial image rendering while validating optional d and p values and image-use rights before publication.
- Test the thumb and gthumb values for compact roster rows and a larger preset on player detail pages, then keep whichever your layout renders best.
- Compare d=low and d=high on a slow mobile connection in your own environment before deciding which one a lightweight app view should request.
- Run an audit job over stored image IDs that records which ones resolve, so broken portraits are caught before a gallery or squad page ships.
Frequently asked questions
How do I build the imageId value?
Take the numeric image ID supplied by another endpoint, such as a player profile, and add the letter c in front of it. The supplied default c231889 shows the form. The ID is passed as a string path segment.
What do the d and p parameters accept?
d is optional and documented as high or low. p is optional, specifies the image size, and is documented as one of de, det, gthumb or thumb. Both can be left out, and values outside those lists are not documented.
What does the endpoint return?
The route ends in i.jpg and the operation is described as getting an image by ID, so expect an image resource rather than JSON. The only supplied response example is an empty object, so the content type and size of the result are not verified.
Were these behaviours observed in a probe?
No. No response was observed for this operation in the supplied probe evidence. The parameter values come from the endpoint documentation, and the effect of each d and p value should be checked with your own request.
Where do I get an image ID?
From other responses that carry an image identifier, for example a player profile. Keep that source ID next to the generated image URL in your data model so you can trace a picture back to the record that supplied it.
Can I publish any image this returns?
Do not assume so. Having the technical ability to request an image does not grant redistribution rights. Check the image-use terms for your product before showing player or editorial pictures publicly.
What should I do if an image does not load?
Confirm the ID has the c prefix, retry without d and p, and fall back to a placeholder avatar in your interface. Coverage of images depends on the ID, and the documentation does not describe an error body.