—Rate this article—
 

Beta Release of SmartDocs

1. In the Resource URL, replace any values enclosed in "{}", such as your organization name.
2. Set the Basic Authentication credentials. These are your Edge credentials (user must be in the Org Admin role).
3. Tweak the Request Body as needed (if a body is needed).
4. Send the live request to Edge and view the response! You can also view Request data.

Add Permissions for Resource to a Role

Resource Summary

Auth Type

BASICAUTH,

Content Type

application/json

Category

Permissions for Resource at Organization Level,

addPermissionatOrgLevel

POST

Add Permissions for Resource to a Role

In Apigee Edge, different user roles are assigned different permissions to view (GET), create (POST), update (PUT), or delete (DELETE) resources in an organization; for example, modifying API proxies or creating custom reports. Management users in those roles are limited to those specific permissions.

Permissions for a user role means assigning verbs to different resources for that role. For example, you can assign verb permissions to the /apis resource in Edge, which is the URI for working with API proxies. (Your organization in the Edge URL is considered the root.) For example, https://enterprise.apigee.com/platform/#/your_org/apis.

Use this API to add resource permissions to a user role. You can use the * wild card in the URI pattern to indicate any value; for example, to include either the 'test' or 'prod' environment in the URI: /environments/*/cache.


Resource URL

https://api.enterprise.apigee.com/v1 /organizations/{org_name}/userroles/{role_name}/permissions

    Header Parameters

  • Name
    Value
    Description
  • Content-Type
    (required)
    Specify the content type

Request Body

org_name Mention the organization name true

role_name Mention the role name true

Basic Auth

OAuth 2

Custom Token

Reset

Make a request and see the response.

Make a request and see the response.

Working...

Help or comments?

  • Something's not working: See Apigee Support
  • Something's wrong with the docs: Click Send Feedback in the lower right.
    (Incorrect? Unclear? Broken link? Typo?)