Updates to Existing APIs

The following section describes updates that have occurred to existing APIs in this release:

Resource	API Name/Endpoint	Method	Function Change Description
Component	Create a custom component /components	POST	Only users assigned the Library Manager role are permitted to invoke the API.
license	Create a custom license /licenses	POST
Edit Custom License /licenses/{licenseId}	PUT
Delete a custom license /licenses/{licenseId}	DELETE
Update Licenses External Id /licenses/{licenseId}	PATCH
Rules	Create Rule /rules	POST
Update Rule /rules	PUT
Delete Rule /rules/{ruleId}	DELETE
User API	manage Permission /users/{loginId}/permission	PUT	This API has been enhanced to assign a new role—library_manager—to existing users, in addition to the previously supported roles: system_admin, edit_policy, and create_project.
Project API	project status /projects/{projectId}/status	PUT	This API has been enhanced with the inclusion of a new field named projectAction , which enables users to manage the locking and unlocking feature of the specified project along with its all associated child projects, based on the project’s status specified in the status field. The projectAction field includes the following dropdown options: Update Status Only—Enables you to only lock and update the status of the specified project. When the status field is set to Project Completed , only the specified project will be locked while all associated child projects will remain unaffected. Lock Child Projects—Enables you to lock the specified project and all its associated child projects. This option is valid only when the status field is set to Project Completed . Unlock Child Projects—Enables you to unlock the specified project and all its associated child projects. This option is valid only when the status field is set to an option other than Project Completed . With this API enhancement, only the Project Administrator is now authorized to successfully invoke the API.