You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Currently, there is no way to configure scopes for API keys. for example, there is no way to have a read-only API key that would not grant you permissions to modify collections/environments or other data, or an API key with a restricted access
Describe the solution you'd like
Introduction of scopes, where team administrators are able to determine the scope of a certain API key
Additional context
The request is raised on the behalf of a user
The text was updated successfully, but these errors were encountered:
Hi!
We introduced a new way to retrieve a collection via an access key, that can be generated in the UI in the "Share" menu of a collection. With this access_key users can retrieve a collection via the Postman API.
See the query params here for more information.
However, the final solution for this would be an OAuth2 approach. We are working on that, but it's a long-term project.
Is your feature request related to a problem? Please describe.
Currently, there is no way to configure scopes for API keys. for example, there is no way to have a read-only API key that would not grant you permissions to modify collections/environments or other data, or an API key with a restricted access
Describe the solution you'd like
Introduction of scopes, where team administrators are able to determine the scope of a certain API key
Additional context
The request is raised on the behalf of a user
The text was updated successfully, but these errors were encountered: