User Management REST APIs

Oracle CPQ 25D introduces a new company-agnostic User REST API endpoint for updating a user. This endpoint includes the auto-generated partyNumber user identification parameter.

Company-agnostic endpoints simplify the management of users on the site by providing a single static endpoint that can be used to update users across all companies. System Integrators no longer need to make separate calls to the Host Company and each Partner Company to manage those users.

Update a User (PUT)

This operation replaces the details of a user with an updated version of the user details.

Note: If your implementation has Oracle CPQ running in Oracle Fusion, the Update a User (PUT) endpoint will replace the details of an existing user and will also create a new user if the Request URI references a user that does not already exist.

• Endpoint:  /rest/v19/users/{partyNumber}
• Method:  PUT

Note: Beginning in v19 when using the new Update a User (PUT) endpoint, any parameters that are not explicitly included in the request body will be set to the default value, including "isAccessAdminPremEnabled" and "isWebServicesOnly" properties. If you are not sending all parameters in the request to update a user, you should use the PATCH method to avoid clearing unspecified properties.

Steps to Enable

Review the REST service definition in the REST API guides to leverage (available from the Oracle Help Center > your apps service area of interest > APIs & Schema). If you are new to Oracle's REST services you may want to begin with the Quick Start section.