API for developers

The whole public symbol catalog is available through a REST API — read access requires no authentication. Build AAC applications on a shared library instead of maintaining your own graphics sets.

Quick start

Search for a symbol (simplified response for integrations):

curl "https://aacstandard.com/api/v1/public/symbols/search?q=water&language=en"

{
  "success": true,
  "data": [
    {
      "id": 123,
      "name": "water",
      "language_code": "en",
      "image_url": "https://aacstandard.com/static/symbols/pl/….png",
      "thumbnail_url": "https://aacstandard.com/static/thumbs/256/symbols/pl/….webp"
    }
  ],
  "count": 1
}

Key endpoints

`GET /api/v1/public/symbols/search`	search: `q`, `language`, `age_group` (child \| youth \| adult \| all), `limit`, `offset`
`GET /api/v1/symbols`	full list with metadata and translations (paginated)
`GET /api/v1/symbols/search`	filters: `q`, `tags`, `age_group`, `has_audio`, `lang`…
`GET /api/v1/symbols/:id`	a single symbol with full metadata
`GET /api/v1/symbols/:id/variant`	person variant: `skin=1–5`, `hair`, `mono=1`, `overlay=plural\|negation` → PNG
`GET /api/v1/symbols/:id/audio`	a TTS recording of the symbol name in a chosen language
`GET /api/v1/translations/languages`	list of supported languages
`GET /api/v1/public/stats`	counts: symbols, languages, groups

Images and thumbnails

Original PNGs (1024×1024) are served from /static/<path>, and light WebP thumbnails from /static/thumbs/{256|512}/<path .webp> — use thumbnails for result grids (~9 KB instead of ~800 KB). Responses carry cache headers (max-age + stale-while-revalidate); thumbnails are immutable for a week.

Rules

The canonical prefix is /api/v1 — the /api alias works but carries a Deprecation header and goes away at the end of 2027.
Public endpoints are rate-limited — cache responses on your side.
Using the symbols in a commercial product requires permission — see the license. A separate partner API exists for reporting missing symbols.

A full API reference (all parameters and error codes) is being prepared for publication — questions: hello@aisay.co.