The WAJD Content API

How it works

Every piece of WAJD content has a stable id and a content hash. The API is read-only and cacheable: your platform polls the manifest, sees what has changed, and fetches only that. Content is static and only grows, so cached responses stay valid.

• Base URL: https://wajd.co.uk/v1
• Auth: send your key as X-API-Key or Authorization: Bearer <key>
• Scopes: each key is licensed for named content types (or all), and is rate-limited and metered per day
• Caching: responses carry an ETag; send If-None-Match to get a fast 304

Endpoints

Method & path	Returns
GET /v1/ping	Health check (no key)
GET /v1/manifest	Catalogue: every content type, its size and version
GET /v1/content/{type}	List items of a type (filter by ?subject=, ?level=, ?year=)
GET /v1/content/{type}/{id}	One full content item
GET /v1/curriculum	The primary spine, Year 1 to the 11 Plus
GET /v1/curriculum/{year}	One year, by subject and term

Content types: curriculum, course, bank, paper, library.

Example

curl -H "X-API-Key: YOUR_KEY" https://wajd.co.uk/v1/curriculum/6

{
  "year": 6, "label": "Year 6", "keyStage": "KS2", "age": "10 to 11",
  "subjects": {
    "Maths": [ { "term": "Autumn", "unit": "Four operations and order",
                 "objective": "Use all four operations with large numbers..." } ],
    "11 Plus": [ ... ]
  }
}

Versioning and sync

Poll GET /v1/manifest and compare each type's version to your last sync. If it is unchanged, you already have the latest. The global version changes whenever any content grows, so a single field tells you if anything is new.