Docs menu

Sportskeeda API endpoint

Sportskeeda guessing-game entities API

Use Crawlora's Sportskeeda guessing-game entities API to extract supported public Sportskeeda data as structured JSON. This page includes request parameters, cURL examples, response schema, error behavior, credit cost, and a Playground link for testing before integration.

GETapiKey4 credits/requestSportskeedapublicnews.sportskeedaGuessingGameEntitiesResponseDoc/sportskeeda/guessing-game-entities

Endpoint facts

Method: GET
API path: /sportskeeda/guessing-game-entities
Auth: apiKey
Credits: 4 credits/request
Platform: Sportskeeda
Response schema: #/definitions/publicnews.sportskeedaGuessingGameEntitiesResponseDoc

Overview

Returns the live public entity list used by a discovered player-guessing game, including the game-specific team, position, and profile fields. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Sportskeeda Scraper API Try Sportskeeda guessing-game entities API in Playground Crawlora API pricing Sportskeeda API documentation

Request parameters

Request parameters are generated from the active endpoint catalog. Required values must be sent before Crawlora can call the upstream public web data source.

Parameter	Type	Required	Default	Description	Example
slug	string	Yes		Discovered host-free game page path Allowed values: wwe/brainbuster-wwe-player-guessing-game, nfl/gridle-nfl-player-guessing-game
x-api-key (header)	string	Yes		API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/sportskeeda/guessing-game-entities?slug=wwe%2Fbrainbuster-wwe-player-guessing-game" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost: 4 credits/request
Charged response: Successful 2xx responses

Plan	Price	Included credits	Daily cap	Rate limit	Overage
Free	$0/mo	2,000	500 daily credits	5/min	No overage
Starter	$9/mo	20,000	5,000 daily credits	15/min	$0.75/1,000 overage credits when enabled
Growth	$29/mo	100,000	25,000 daily credits	45/min	$0.45/1,000 overage credits when enabled
Pro	$79/mo	400,000	No daily cap	120/min	$0.30/1,000 overage credits
Business	$199/mo	1,200,000	No daily cap	300/min	$0.20/1,000 overage credits
Enterprise	$499/mo	5,000,000	No daily cap	1,000/min	$0.12/1,000 overage credits

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

Proxy strategy: managed automatically where needed
Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
Browser cluster: supported dynamic workloads can be routed through distributed browser instances
Retry behavior: automatic retry/fallback may be used depending on endpoint type
Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
Billing: credits are charged only for successful 2xx responses
Observability: responses include request context where available

Response behavior

Returns the full public entity list used by the selected game. WWE records include fields such as aliases, height, brand, Hall of Fame, and WrestleMania appearances; NFL records include conference, division, team, position, uniform, and experience. The upstream `includeDeleted=true` behavior is fixed to match the public game client; it is not a caller-selectable filter. The response preserves the per-game optional fields and omits fields that do not apply to a record.

Catalog quality warnings

missing example for required query param: slug

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

Status	Common failure case
400	Invalid input or missing required parameter
429	Plan or endpoint rate limit exceeded
500	Internal execution error
502	Upstream platform failed, returned unusable HTML, or served a challenge page that could not be resolved

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Failure responses

Status	Description	Schema
400	Bad Request	#/definitions/app.Response
404	Not Found	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Example JSON response

{
  "data": {
    "slug": "nfl/gridle-nfl-player-guessing-game",
    "game_slug": "gridle-nfl-player-guessing-game",
    "entities": [
      {
        "id": "example-player-id",
        "identifier": "ZXhhbXBsZQ==",
        "name": "Example Player",
        "team": "Example Team",
        "position": "Quarterback",
        "conference": "AFC",
        "division": "East"
      }
    ]
  }
}

Request schema

No body schema

Response schema

#/definitions/publicnews.sportskeedaGuessingGameEntitiesResponseDoc

Field	Type	Required
data	sportskeeda.GuessingGameEntitiesResponse	No
data.entities	array	No
data.entities[].age_at_death	integer	No
data.entities[].alias1	string	No
data.entities[].brand	string	No
data.entities[].conference	string	No
data.entities[].date_of_birth	string	No
data.entities[].dead	string	No
data.entities[].division	string	No
data.entities[].experience	string	No
data.entities[].gender	string	No
data.entities[].hall_of_fame	string	No
data.entities[].height_in_inches	integer	No
data.entities[].id	string	No
data.entities[].identifier	string	No
data.entities[].name	string	No
data.entities[].position	string	No
data.entities[].team	string	No
data.entities[].touchdowns	integer	No
data.entities[].uniform	integer	No
data.entities[].wrestlemania_appearances	integer	No
data.game_slug	string	No
data.slug	string	No

Code examples

Use environment variables for secrets and keep Crawlora API keys server-side.

curl -X GET "https://api.crawlora.net/api/v1/sportskeeda/guessing-game-entities?slug=wwe%2Fbrainbuster-wwe-player-guessing-game" \
  -H "x-api-key: $CRAWLORA_API_KEY"

Responsible public web data workflows

Crawlora is designed for responsible structured public web data workflows. Customers are responsible for using Crawlora in compliance with applicable laws, third-party rights, target-platform rules, and Crawlora terms.

Read Crawlora terms

More Sportskeeda endpoint docs Sportskeeda Scraper API Crawlora API pricing Try Sportskeeda guessing-game entities API in Playground Sportskeeda article API documentation Sportskeeda author API documentation Sportskeeda College Schedule Options API documentation Sportskeeda College Schedule API documentation Sportskeeda Cricket Commentary API documentation Sportskeeda Cricket Match API documentation

Open in Playground Back to group