Create Release Phases Bulk — POST /api/v1/releases/{release_id}/phases/bulk

Create Release Phases Bulk

Create a release’s first schedule in one request.

Endpoint: POST /api/v1/releases/{release_id}/phases/bulk

Authentication: Send a signed-in user’s access token in Authorization: Bearer <access token>, or an API key in X-API-Key: <API key>.

• Your role must be QA lead or higher.
• You must have access to this release.

Parameters

Name	In	Required	Type	Default	Description
release_id	path	yes	string
X-API-Key	header	no	string or null		API key, as an alternative to the access token (see Authentication).

Request body

Content type	Body	Required
application/json	ReleasePhasesBulkRequest	yes

Responses

Status	Meaning	Body
201	Successful Response	ReleasePhasesCreatedResponse (application/json)
422	Validation Error	HTTPValidationError (application/json)

It can also return 401 if your credential is missing or expired, 403 if your credential does not allow this request, and 404 if the item does not exist or you cannot see it. Your role, your project membership and the key’s scope decide what a credential allows. See Errors and retries.

More details

• Group: Releases
• Operation ID: create_release_phases_bulk_api_v1_releases__release_id__phases_bulk_post
• Source code: backend/app/routers/releases.py, line 914
• Specification: OpenAPI JSON