Skip to content
TestLookupTestLookup
Search Ctrl K

Search TestLookup

Enter a term to search the local static index.

    Update Phase — PUT /api/v1/releases/{release_id}/phases/{phase_id}

    Update Phase

    Endpoint: PUT /api/v1/releases/{release_id}/phases/{phase_id}

    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

    Section titled “Parameters”
    NameInRequiredTypeDefaultDescription
    release_idpathyesstring
    phase_idpathyesstring
    X-API-Keyheadernostring or nullAPI key, as an alternative to the access token (see Authentication).

    Request body

    Section titled “Request body”
    Content typeBodyRequired
    application/jsonPhaseUpdateyes

    Responses

    Section titled “Responses”
    StatusMeaningBody
    200Successful ResponseNot documented (application/json)
    422Validation ErrorHTTPValidationError (application/json)

    Response fields not documented. The API specification does not describe the body of every response this endpoint returns, so this page cannot list those fields. The body is not empty. To see it, call the endpoint on your own installation. All endpoints with undocumented responses.

    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

    Section titled “More details”