Querying About Scoped API Keys Usage in Typesense
TLDR Rajeev requested information about appropriate scoped API keys for a retrieve call on a collection in Typesense. Jason clarified that collections:get
is the appropriate key needed.
1
Jul 20, 2022 (15 months ago)
Rajeev
04:20 PMQuick question regarding the scoped API keys, what is the scope that one needs to use if they want to do a retrieve call on a collection, I see as per the documentation for collections there are three scopes but none of them are read only. We are trying to do this to get schema related information of the collection and based on it do some custom rendering on the client side.
Jason
04:22 PMYou want to use
collections:get
Rajeev
04:24 PMJason
04:26 PMIf the last component of the API path is /XYZ then the resource name in permissions is
XYZ:action
where action can be get
, delete
, create
Rajeev
04:27 PM1
Typesense
Indexed 2779 threads (79% resolved)
Similar Threads
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.
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.
Issues with Generating Scope API Keys in Python
Danny had issues generating a valid scope API key in a Python GraphQL server. Jason suggested encoding changes and confirmed that the key length varies. Issue unresolved with Python, although JS library worked.