Docs menu

Rotten Tomatoes API endpoint

Rotten Tomatoes Critics Directory API

Use Crawlora's Rotten Tomatoes Critics Directory API to extract supported public Rotten Tomatoes 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.

GETapiKey2 credits/requestRotten Tomatoesrottentomatoes.criticsAuthorsResponseDoc/rottentomatoes/critics/authors

Endpoint facts

Method: GET
API path: /rottentomatoes/critics/authors
Auth: apiKey
Credits: 2 credits/request
Platform: Rotten Tomatoes
Response schema: #/definitions/rottentomatoes.criticsAuthorsResponseDoc

Overview

Returns current or inactive critics from Rotten Tomatoes' public author directory. Browse one letter or search by name; use `next_cursor` as `after` or `previous_cursor` as `before`, as indicated by the corresponding page flag. The letter values come from the live directory controls. 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.

Rotten Tomatoes Scraper API Try Rotten Tomatoes Critics Directory API in Playground Crawlora API pricing Rotten Tomatoes 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
letter	string	No	Directory letter. Omit when using search; default a. Allowed values: #, a, b, c, d, e, f, g, h, i, j, k, l, m, n, o, p, q, r, s, t, u, v, w, x, y, z
search	string	No	Search critics by name; cannot be combined with letter
inactive	boolean	No	Include the site's inactive critics list
after	string	No	Opaque cursor from data.next_cursor
before	string	No	Opaque cursor from data.previous_cursor; cannot be combined with after
limit	integer	No	Rows per page, default 100, range 1 to 100
x-api-key (header)	string	Yes	API key required

cURL example

curl -X GET "https://api.crawlora.net/api/v1/rottentomatoes/critics/authors?letter=%23&inactive=true&limit=10" \
  -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: 2 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

Each critic includes their public directory path, approval badges, and affiliated publications when present. An empty author list is a valid no-results response. The response includes forward and backward page flags and cursors.

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
429	Too Many Requests	#/definitions/app.Response
500	Internal Server Error	#/definitions/app.Response
503	Service Unavailable	#/definitions/app.Response

Example JSON response

{
  "code": 200,
  "msg": "OK",
  "data": {
    "letter": "a",
    "inactive": false,
    "limit": 3,
    "has_next_page": true,
    "next_cursor": "MQ==",
    "has_previous_page": false,
    "authors": [
      {
        "name": "Ganesh Aaglave",
        "path": "/critics/ganesh-aaglave",
        "publication_label": "when published by",
        "publications": [
          {
            "id": "2784",
            "name": "Firstpost",
            "path": "/critics/source/2784",
            "editorial_url": "http://www.firstpost.com/tag/moviereview"
          }
        ]
      }
    ],
    "source_url": "https://www.rottentomatoes.com/napi/critics/authors?isInactiveCriticsList=false&letter=a&pageCount=3&userToken=null",
    "public_page_derived": true
  }
}

Request schema

No body schema

Response schema

#/definitions/rottentomatoes.criticsAuthorsResponseDoc

Field	Type	Required	Example
code	integer	No	200
data	rottentomatoes.CriticsAuthorsResponse	No
data.after	string	No
data.authors	array	No
data.authors[].badges	array	No	Individually approved
data.authors[].name	string	No	Mae Abdulbaki
data.authors[].path	string	No	/critics/mae-abdulbaki
data.authors[].publication_label	string	No	when published by
data.authors[].publications	array	No
data.authors[].publications[].editorial_url	string	No	https://example.com/reviews
data.authors[].publications[].id	string	No	2784
data.authors[].publications[].name	string	No	Firstpost
data.authors[].publications[].path	string	No	/critics/source/2784
data.before	string	No
data.fetched_at	string	No	2026-09-26T10:00:00Z
data.has_next_page	boolean	No	true
data.has_previous_page	boolean	No	false
data.inactive	boolean	No	false
data.letter	string	No	a
data.limit	integer	No	100
data.next_cursor	string	No	MQ==
data.previous_cursor	string	No	MA==
data.public_page_derived	boolean	No	true
data.search	string	No
data.source_url	string	No	https://www.rottentomatoes.com/napi/critics/authors?isInactiveCriticsList=false&letter=a&pageCount=100&userToken=null
msg	string	No	OK

Code examples

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

curl -X GET "https://api.crawlora.net/api/v1/rottentomatoes/critics/authors?letter=%23&inactive=true&limit=10" \
  -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 Rotten Tomatoes endpoint docs Rotten Tomatoes Scraper API Crawlora API pricing Try Rotten Tomatoes Critics Directory API in Playground Rotten Tomatoes browse filters API documentation Rotten Tomatoes movie discovery rows API documentation Rotten Tomatoes TV discovery rows API documentation Rotten Tomatoes Editorial Content API documentation Rotten Tomatoes Editorial Detail API documentation Rotten Tomatoes editorial search API documentation

Open in Playground Back to group