Create Permission Policy
Changed onCreate a new Permission Policy
NOTE: When you set up a policy statement for this call using the permissionPolicy request parameter to specify the effect, action, and resource, you must use all lower case and the format as shown in this example for a Permission Policy statement that grants full CRUD access to all meters:
"permissionPolicy" : [
{
"effect" : "allow",
"action" : [
"config:create",
"config:delete",
"config:retrieve",
"config:update"
]
"resource" : [
"config:meter/*"
]
}
]
For more details and further examples, see Understanding, Creating, and Managing Permission Policies in our main Documentation.
Request
- Base URLhttps://api.m3ter.com
- AuthOAuth 2Authorization codehttps://m3ter.auth.us-east-1.amazoncognito.com/oauth2/authorize, token URL https://m3ter.auth.us-east-1.amazoncognito.com/oauth2/tokenClient credentialsToken URL /oauth/token
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
UUID of the organization
Request body
Response
Returns the new Permission Policy
Changes
- breaking
the
response's property type changed from no type toobjectfor status
- breaking
- warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - warning
removed the optional property
from the response with the status - info
added the new
AUDIT_RETRIEVEenum value to the request property/// - info
added
subschema #2to the response bodyallOflist for the response status
- warning