Create a subproject
Creates a subproject under the authenticated root project.
Creating a project is only allowed when authenticated as a top-level (root) project. A subproject cannot itself contain subprojects, so attempting to create one while authenticated as a subproject fails with 422 nested_subprojects_not_allowed.
The response includes the signing_key. This is the only time it is returned — it cannot be retrieved through the API afterward, so capture it from this response.
Use a subproject to isolate settings and resources beneath a root project. Integrations built around Compatibility API Account SIDs can use Create subprojects instead.
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.
Request body
Example request
{
"name": "Acme Staging",
"protect_recordings": true,
"force_https_requests": true
}Response
The request has succeeded and a new resource has been created as a result.
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",
"signing_key": "PSK_4d8c2b1a9f3e7c6d5b4a3e2f1d0c9b8a"
}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.