- HTTP request
 - Path parameters
 - Query parameters
 - Request body
 - Response body
 - Authorization scopes
 - Examples
 - Try it!
 
Deletes a custom Role.
When you delete a custom role, the following changes occur immediately:
- You cannot bind a principal to the custom role in an IAM 
Policy. - Existing bindings to the custom role are not changed, but they have no effect.
 - By default, the response from 
roles.listdoes not include the custom role. 
A deleted custom role still counts toward the custom role limit until it is permanently deleted. You have 7 days to undelete the custom role. After 7 days, the following changes occur:
- The custom role is permanently deleted and cannot be recovered.
 - If an IAM policy contains a binding to the custom role, the binding is permanently removed.
 - The custom role no longer counts toward your custom role limit.
 
HTTP request
DELETE https://iam.s3nsapis.fr/v1/{name=projects/*/roles/*}
The URL uses gRPC Transcoding syntax.
Path parameters
| Parameters | |
|---|---|
name | 
                
                   
 The  
 Note: Wildcard (*) values are invalid; you must specify a complete project ID or organization ID. Authorization requires the following IAM permission on the specified resource  
  | 
              
Query parameters
| Parameters | |
|---|---|
etag | 
                
                   
 Used to perform a consistent read-modify-write. A base64-encoded string.  | 
              
Request body
The request body must be empty.
Response body
If successful, the response body contains an instance of Role.
Authorization scopes
Requires one of the following OAuth scopes:
https://www.googleapis.com/auth/iamhttps://www.googleapis.com/auth/cloud-platform
For more information, see the Authentication Overview.