Update a project
Changes the name and security settings of a root project or subproject in the caller's project tree. Use it to control media protection and HTTPS requirements; project API tokens are managed separately through Project Tokens. Compatibility API Accounts use their own SID-based update route.
Permissions
The API token used to authenticate must have the following scope(s) enabled to make a successful request: Management.
Learn more about API scopes.
Path parameters
Universal Unique Identifier.
The unique identifier of the project or subproject.
Request body
Example request
{
"name": "Acme Staging (EU)",
"protect_recordings": true,
"protect_message_media": true,
"force_https_requests": true
}Response
The request has succeeded.
Example response
{
"name": "Acme Staging",
"subproject": true,
"region_preference": "us-west",
"force_https_requests": true,
"created_at": "2024-05-06T12:20:00Z",
"updated_at": "2024-05-06T12:20:00Z"
}Changes
Changed in 2 of the 137 revisions of this API.3
- ○
added the non-success response with the status
500response-non-success-status-added
- ○
removed the non-success response with the status
403response-non-success-status-removed
This revision also has 1 change that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
- ○
endpoint added
endpoint-added
This revision also has 42 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
- ○
Of the 137 revisions, 3 have a changelog that could not be searched.