Issue with API Key Format and Typesense API Calls
TLDR Adrian encountered a 401 error when making API calls using a key, and Jason helped correct the key's format. Adrian then created a Github issue about the problem.
3
Aug 26, 2023 (1 month ago)
Adrian
03:20 PMcurl "http://...:8108/keys" \
-X POST \
-H "X-TYPESENSE-API-KEY: ${TYPESENSE_API_KEY}" \
-H 'Content-Type: application/json' \
-d '{"description":"Key with custom permissions","actions": ["collections:*,documents:*,aliases:*,synonyms:*"], "collections": ["*"]}'
Jason
03:20 PMJason
03:21 PM["collections:*", "documents:*", "aliases:*, "synonyms:*"]Adrian
03:21 PMAdrian
03:21 PM1
Jason
03:21 PM1
Aug 27, 2023 (1 month ago)
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
Correct API Key Generation and Usage on Cloud
Tom faced 401 errors while creating keys via the Cloud API. Kishore Nallan clarified the correct syntax and mechanics, and identified a header mislabeling on Tom's part that caused the issue. They also discussed using scoped API keys.
Typesense v0.24.0 API Key Issue with Multiple Actions
Hariharan is facing an issue with Typesense API keys when combining "documents:search" and "documents:export" actions. Jason asks for a curl command snippet to replicate the issue.
Resolving Issues with Scoped API Keys in Typesense with Golang
Suvarna had problems with generating and using scoped API keys in Typesense with Golang. Several bugs misleading the user were found and fixed by Kishore Nallan.