Get a Tes teaching resource API

Endpoint facts

Method

GET

API path

/tes/resources/detail

Auth

apiKey

Credits

1 credit/request

Platform

Tes

Response schema

#/definitions/tes.resourceDetailResponseDoc

Overview

Returns normalized detail for one teaching resource by its numeric id (the id field returned by tes-resource-search). Descriptive facts (title, subject, age range, resource type, author, price, rating, licence label), a per-file attachment list (file type, size, and a preview thumbnail -- metadata only), and the most recent page of reviews are returned -- not the downloadable resource file itself, which robots.txt already disallows scraping regardless. 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.

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

1 credit/request

Charged response

Successful 2xx responses

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

- An unknown or no-longer-listed resource id returns `404`. - `id` resolves purely from the numeric id -- the real listing's slug does not need to be known. - `price` is `0` and `free` is `true` for free resources. - `reviews` is the most recent page of reviews (as many as the resource's own page shows, typically up to 5); `rating_count` is the true total review count across every review, not just `len(reviews)`. A resource with no reviews yet returns an empty `reviews` array. - `license` is the resource's own licence label as Tes's detail page displays it, e.g. `Tes paid licence` or `Creative Commons "Sharealike"`. - `attachments` lists each downloadable file's own type, size, and a preview thumbnail image -- metadata only; the file itself is never fetched (robots.txt already disallows `/teaching-resource/download/`). Example response: ```json { "code": 200, "msg": "OK", "data": { "id": "13463100", "title": "Phonics Bunting", "url": "https://www.tes.com/teaching-resource/x-13463100", "description": "These are A-Z alphabet bunting designed using the Little Wandle phonics scheme.", "author": "joannecrozierharbottle", "author_url": "https://www.tes.com/teaching-resources/shop/joannecrozierharbottle", "subject": "English", "age_range": "3-5", "resource_type": "Visual aid/Display", "price": 1, "currency": "GBP", "free": false, "rating": 4.2, "rating_count": 5, "thumbnail_url": "https://d1e4pidl3fu268.cloudfront.net/example/preview.png", "license": "Tes paid licence", "attachments": [ { "file_type": "png", "size": "256.71 KB", "preview_image_url": "https://d1uvxqwmcz8fl1.cloudfront.net/tes/resources/13463100/one/image?width=500" } ], "reviews": [ { "id": "1313111", "rating": 5, "comment": "Thank you, great resource", "author": "jafgthomas", "author_url": "https://www.tes.com/teaching-resources/shop/jafgthomas", "posted": "8 years ago" } ] } } ```

Error behavior

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

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

Related