API Endpoints

This overview has been superseded by the full API Reference — a complete, always-up-to-date reference generated from the live OpenAPI specification, with request and response schemas, cURL/JavaScript/Python examples and an in-browser playground.

All endpoints are prefixed with /api/v1/. The API Reference documents every public endpoint group:

Authentication — login, refresh, logout
API Tokens — create and manage lh_ tokens
Organizations, Users, User Groups
Courses, Chapters, Activities, Blocks
Assignments — including headless grading flows
Folders, Media, Certifications
Payments, Search, Analytics
Webhooks and Headless server-to-server endpoints

Common Patterns

All endpoints are prefixed with /api/v1/.
Resources follow standard REST conventions: GET to list or retrieve, POST to create, PUT to update, DELETE to remove.
Create/update endpoints commonly accept multipart form data rather than JSON, since many also accept file uploads (e.g. thumbnails, avatars).
Authenticated endpoints require either the Authorization: Bearer <token> header or the access_token_cookie cookie.
Programmatic access uses API tokens with the lh_ prefix (Pro plan).
Responses are returned as JSON.

For a local development instance, the interactive Swagger UI also remains available at http://localhost:1338/docs .

PreviousAPI Authentication NextHeadless Assignments