Skip to content

docs(api-keys): add synonym_sets action scope and migration notice#437

Open
alangmartini wants to merge 3 commits intotypesense:masterfrom
alangmartini:docs/synonym-sets-api-key-actions
Open

docs(api-keys): add synonym_sets action scope and migration notice#437
alangmartini wants to merge 3 commits intotypesense:masterfrom
alangmartini:docs/synonym-sets-api-key-actions

Conversation

@alangmartini
Copy link
Contributor

@alangmartini alangmartini commented Feb 6, 2026

Summary

  • Adds the new synonym_sets:* API key action scope to the v30.0 and v30.1 API Keys documentation
  • Adds a warning box explaining the breaking change: API keys scoped to synonyms:* do not grant access to the new /synonym_sets endpoints, resulting in 401 Unauthorized errors
  • Documents the migration path: create new keys with synonym_sets:* actions, then delete old keys (since there is no update endpoint for API keys)
  • Renames the existing "Synonym actions" section to "Synonym actions (Collection-level)" to clarify these still apply to legacy /collections/{collection}/synonyms endpoints

Context

When upgrading to v30, the synonym API route changed from /collections/{collection}/synonyms to /synonym_sets. Since Typesense derives API key action scopes from the API route + operation, any existing API keys using synonyms:* actions will not work with the new synonym sets endpoints.

In v30, the synonym API route changed from /collections/{id}/synonyms
to /synonym_sets, which means API keys scoped to synonyms:* actions
no longer grant access to the new endpoints. This adds the new
synonym_sets:* actions and documents the migration path.
Move the breaking change notice about synonym API key actions from the
api-keys page into the deprecations/behavior changes section of the
changelog where users are more likely to see it during upgrades.
Users landing on the synonyms docs page should also see the notice
about needing to update their API key actions from synonyms:* to
synonym_sets:* when upgrading to v30.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant