Update the specified project.
For updates, all properties are optional. The request payload only needs to contain the properties that you would like to update.
Authorization header with valid Bearer token for scope
For more documentation on authorization and how to get access token visit OAUTH2 Authorization page.
If a user is affiliated with an Organization, then the user must be an Organization Administrator in order to update a project that is owned by the Organization.
Example: email@example.com is an Organization Administrator that works for Stark Industries that has an account with Bentley. John will be able to update any project that belongs to Stark Industries.
An Organization Administrator must have at least one of the following roles assigned in User Management: Account Administrator, Co-Administrator, or CONNECT Services Administrator. For more information about User Management please visit our Bentley Communities Licensing, Cloud, and Web Services wiki page.
A user that is not affiliated with an Organization can update projects that are owned by the user account.
Example: firstname.lastname@example.org is an independent contractor that does not have an account with Bentley. Jane will be able to update any project that belong to Jane. Jane owns any project that she created.
This response indicates that request lacks valid authentication credentials. Access token might not been provided, issued by the wrong issuer, does not have required scopes or request headers were malformed.
The user has insufficient permissions for the requested operation.
This response indicates that one of the associated entities could not be found.
Invalid request to update a project. Review the 'Field Values' section near the top of this page.
This response indicates that the user has sent too many requests in a given amount of time.