Developer Platform
Build on the Coptic grammar dataset
The grammar API exposes a read-only, versioned dataset for lessons, concepts, examples, exercises, footnotes, and sources. Start with the developer guide, then move into Swagger or the raw OpenAPI document when you are ready to integrate.
Start here
Most integrations should begin with the API index, which documents the available resource families and the current dataset version.
Typical workflow
- Call /api/v1/grammar to discover the current endpoints and dataset version.
- Fetch /api/v1/grammar/lessons for the published lesson index.
- Load /api/v1/grammar/lessons/[slug] for full lesson payloads.
- Use /api/openapi.json when generating clients or importing the schema into tooling.
High-value endpoints
Developers
Integration notes
- Responses are read-only and versioned with schemaVersion, datasetVersion, and generatedAt metadata.
- The public dataset only exposes published lessons and their related concepts, examples, exercises, footnotes, and sources.
- The lesson filter accepts either a lesson slug or a canonical lesson id.
- For browser apps on another origin, a backend proxy is the safest default.
Example request
A minimal server-side fetch that lists published lesson titles.
const response = await fetch(
"https://kyrilloswannes.com/api/v1/grammar/lessons",
);
const payload = await response.json();
const lessonTitles = payload.data.map((lesson) => lesson.title.en);