Max Priazhevskii
02/18/2026, 2:32 AMsynonyms:* and overrides:* actions. After upgrading to v30.1, those keys no longer have access to the new synonym sets and curation sets endpoints. We tried adding synonym_sets:* and curation_sets:* but it still doesn’t work. What are the correct API key actions strings for the new sets?Kishore Nallan
02/18/2026, 5:14 AMMax Priazhevskii
02/18/2026, 5:42 AMsynonym_sets:* in place we can fetch the set(s), but not set items:
/synonym_sets/{name}/items
Is there another permission we need to allow access to items? Same question for curation set items.Kishore Nallan
02/18/2026, 5:46 AMsynonym_sets:createMax Priazhevskii
02/18/2026, 5:47 AMMax Priazhevskii
02/18/2026, 5:52 AMMax Priazhevskii
02/18/2026, 5:56 AM{
"actions": [
"collections:*",
"documents:*",
"aliases:*",
"synonym_sets:list",
"synonym_sets:get",
"synonym_sets:create",
"synonym_sets:delete",
"curation_sets:*",
"metrics.json:list",
"stats.json:list",
"debug:list"
],
"autodelete": false,
"collections": [
"{prefix}:.*"
],
"description": "{prefix}",
"expires_at": 64723363199,
"id": 226,
"value_prefix": "S4n7"
}Kishore Nallan
02/18/2026, 5:56 AMFanis Tharropoulos
02/18/2026, 4:36 PMsynonym_sets/items:*. You should include both as ["synonym_sets:*","synonym_sets/items:*"] in order to have access to both the top-level resource and the sub-level sub-resource for the itemsMax Priazhevskii
02/18/2026, 5:43 PM{
"actions": [
"collections:*",
"synonym_sets:*",
"synonym_sets/items:*",
],
"collections": [
"{prefix}:.*"
],
"synonym_sets": [
"{prefix}:.*"
],
cc @Kishore NallanFanis Tharropoulos
02/19/2026, 9:30 AMMax Priazhevskii
02/19/2026, 8:55 PMAlan Martini
03/17/2026, 3:26 PMMax Priazhevskii
04/14/2026, 4:41 AM