Docs menu

Sportskeeda API endpoint

Sportskeeda structured page data API

Use Crawlora's Sportskeeda structured page data 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.sportskeedaTablesResponseDoc/sportskeeda/page-data

Endpoint facts

Method: GET
API path: /sportskeeda/page-data
Auth: apiKey
Credits: 4 credits/request
Platform: Sportskeeda
Response schema: #/definitions/publicnews.sportskeedaTablesResponseDoc

Overview

Returns server-rendered team, player, roster, leaderboard, ranking, depth, playoff, and game-log tables. NFL team stats include team-leader cards, player-category tables, and Basic, Advanced, and Expert team tables. Season and type are accepted only if offered by the selected page; discover their values with page-options. Player game-log seasons use their discovered season-specific path and return every table offered by the page; NFL category tabs are listed by page-options. College-football schedule slugs accept a discovered conference slug and filter the embedded schedule rows locally; an offered group with no games on that week returns status no_data. The trade value chart uses its public JSON asset and has a separate endpoint. A page with no structured tables returns an upstream error. 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 structured page data 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	Description
slug	string	Yes	Sportskeeda path without host
season	integer	No	Season year offered by this page's page-options filter
type	string	No	Season phase offered by this page's page-options filter; leaderboard pages offer pre, regular, post
conference	string	No	College-football schedule conference slug from page-options Allowed values: all-conferences, all-fbs-i-a, atlantic-coast, big-ten, mid-american, pac-12, southeastern, independents-fbs, big-12, conference-usa, mountain-west, sun-belt, aac, all-fcs-i-aa, big-sky, missouri-valley, ivy-league, mid-eastern-athletic, ohio-valley, patriot-league, pioneer-league, southern, southland, swac, northeast, independents-fcs, big-south, caa, united-athletic
x-api-key (header)	string	Yes	API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/sportskeeda/page-data?conference=all-conferences" \
  -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

Browser cluster behavior

Some targets require real browser execution because the data is loaded through JavaScript, dynamic rendering, or interaction-like browser behavior.

For supported endpoints, Crawlora can route requests through a managed browser cluster. This allows Crawlora to execute JavaScript, load dynamic content, apply browser-level request behavior, and normalize the rendered result into JSON.

You do not need to operate your own Playwright, Puppeteer, Chrome, proxy, queue, or retry infrastructure.

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/team-stat/net-yards-per-game-leaders",
    "title": "NFL Regular Team Stats 2026-27",
    "tables": [
      {
        "columns": [
          "Team",
          "GP",
          "TotYds"
        ],
        "rows": [
          [
            {
              "text": "Chicago Bears",
              "slug": "nfl/chicago-bears"
            },
            {
              "text": "2"
            },
            {
              "text": "849"
            }
          ]
        ]
      }
    ],
    "views": []
  }
}

Request schema

No body schema

Response schema

#/definitions/publicnews.sportskeedaTablesResponseDoc

Field	Type	Required
data	sportskeeda.TablesResponse	No
data.matches	array	No
data.matches[].competition	string	No
data.matches[].date_time	string	No
data.matches[].result	string	No
data.matches[].score_1	string	No
data.matches[].score_2	string	No
data.matches[].slug	string	No
data.matches[].status	string	No
data.matches[].team_1	string	No
data.matches[].team_2	string	No
data.matches[].venue	string	No
data.slug	string	No
data.status	string	No
data.tables	array	No
data.tables[].columns	array	No
data.tables[].name	string	No
data.tables[].rows	array	No
data.title	string	No
data.views	array	No
data.views[].name	string	No
data.views[].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/page-data?conference=all-conferences" \
  -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 structured page data 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