Search the Tes Schools Directory API

Endpoint facts

Method

GET

API path

/tes/schools/search

Auth

apiKey

Credits

1 credit/request

Platform

Tes

Response schema

#/definitions/tes.schoolSearchResponseDoc

Overview

Searches Tes's (tes.com) public Schools Directory by school name or location. Returns normalized listing facts (name, logo, a short description, address) for each matching school/employer. Each result's id is the same employer id tes-job-employer accepts, so a caller can go straight from a name/location search to a full employer profile (school type/phase/funding status/gender/age range, and its currently-open positions) without first needing a job posting to discover the id. 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

- `total`/`total_pages` are the upstream's true counts across all pages, not just the current page's length. - A query with no matches returns a well-formed empty `schools` array, not an error. - `address` joins whichever address lines the upstream provides (not every school has all three); it can be empty for a school with no address on file. Example response: ```json { "code": 200, "msg": "OK", "data": { "query": "Epsom", "page": 1, "page_size": 20, "total_pages": 1, "total": 6, "schools": [ { "id": "1039424", "name": "Epsom College", "url": "https://www.tes.com/jobs/employer/epsom-college-1039424", "logo_url": "https://d2yw9izrmawh7r.cloudfront.net/employers/1039424/brandimages/20181030_1126AM_desktop_1039424_logo.jpg", "description": "The College has grown significantly in the past seven years.", "address": "College Road", "country": "United Kingdom", "post_code": "KT17 4JQ" } ] } } ```

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