Get roles by admin user ID or API Key
Retrieves License Manager roles of a particular admin user or API key.
Permissions
Any user or API key must have at least one of the appropriate License Manager resources to be able to successfully run this request. Otherwise they will receive a status code 403 error. These are the applicable resources for this endpoint:
| Product | Category | Resource |
|---|---|---|
| License Manager | Services access control | Find user by email |
There are no applicable predefined roles for this resource list. You must create a custom role and add at least one of the resources above in order to use this endpoint. To learn more about machine authentication at VTEX, see Authentication overview.
❗ To prevent integrations from having excessive permissions, consider the best practices for managing app keys when assigning License Manager roles to integrations.
Path parameters
ID of the user.
Headers
Type of the content being sent.
HTTP Client Negotiation Accept Header. Indicates the types of responses the client can understand.
Response
Success
Changes
Changed in 7 of the 50 revisions of this API.571
- ▲
added the new required
headerrequest parameterAcceptnew-required-request-parameter
- ▲
- ●
deleted the
pathrequest parameteraccountNamerequest-parameter-removed
- ●
deleted the
pathrequest parameterenvironmentrequest-parameter-removed
- ●
- ●
deleted the
pathrequest parameterenvironmentrequest-parameter-removed
- ○
added the media type
application/jsonfor the response with the status200response-media-type-added
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ●
- ▲
added the new path request parameter
environmentnew-request-path-parameter
- ●
deleted the
pathrequest parameterenvironmentrequest-parameter-removed
- ▲
- ▲
added the new path request parameter
environmentnew-request-path-parameter
- ●
deleted the
pathrequest parameterenvironmentrequest-parameter-removed
- ▲
- ▲
added the new path request parameter
environmentnew-request-path-parameter
- ●
deleted the
pathrequest parameterenvironmentrequest-parameter-removed
- ▲
- ▲
added the new path request parameter
environmentnew-request-path-parameter
- ●
deleted the
pathrequest parameterenvironmentrequest-parameter-removed
- ▲