Delete a role assignment

delete

/hcmRestApi/resources/11.13.18.05/userAccounts/{GUID}/child/userAccountRoles/{UserRoleId}

Request

Path Parameters
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
  • The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
  • If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
  • The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.

There's no request body for this operation.

Back to Top

Response

Default Response

No Content. This task does not return elements in the response body.
Back to Top

Examples

The following example shows how to delete a role assignment by submitting a DELETE request on the REST resource using cURL.

curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -X DELETE "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/userAccounts/8A8D6884309FD869E050F50A9C4E9A00/child/userAccountRoles/300100185248805"

Example of Response Header

The following is an example of the response header.

Status: HTTP/1.1 204 No Content
Content-Type : text/plain

Example of Response Body

The following example shows the contents of the response body in JSON format.

HTTP/1.1 204 No Content
Back to Top