PUT /v2/projects/{project_id}

To update a project, send a PUT request to /v2/projects/$PROJECT_ID. All of the following attributes must be sent.

Servers

Path parameters

Name Type Required Description
project_id String Yes

A unique identifier for a project.

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Request body fields

Name Type Required Description
id String No

The unique universal identifier of this project.

is_default Boolean Yes

If true, all resources will be added to this project if no project is specified.

name String Yes

The human-readable name for the project. The maximum length is 175 characters and the name must be unique.

owner_uuid String No

The unique universal identifier of the project owner.

description String Yes

The description of the project. The maximum length is 255 characters.

purpose String Yes

The purpose of the project. The maximum length is 255 characters. It can have one of the following values:

  • Just trying out DigitalOcean
  • Class project / Educational purposes
  • Website or blog
  • Web Application
  • Service or API
  • Mobile Application
  • Machine learning / AI / Data processing
  • IoT
  • Operational / Developer tooling

If another value for purpose is specified, for example, "your custom purpose", your purpose will be stored as Other: your custom purpose.

environment String Yes

The environment of the project's resources.

Possible values:

  • "Development"
  • "Production"
  • "Staging"
created_at String No

A time value given in ISO8601 combined date and time format that represents when the project was created.

owner_id Integer No

The integer id of the project owner.

updated_at String No

A time value given in ISO8601 combined date and time format that represents when the project was updated.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.