HTTP - Management
Removed from your favourites
Mark a block version as broken
Created by s.horan, last modified by zengenti on 17 Jan 2023
Marking a block version as broken ensures that it cannot be released to be used in production. If a released version that is currently live is marked as broken, then it is rolled back.
POST/api/management/projects/{projectId}/blocks/{blockId}/actions
Parameters
Name | Parameter type | Type | Description | Example | Required |
---|---|---|---|---|---|
projectId | path | string | The project identifier found in the project overview screen of the management console | movieDb | true |
blockId | path | string | The block identifier | movie-listing | true |
Example
Mark version 2 of the movie-listing block as broken
JSON
Accept: application/json
POST: /api/management/projects/movieDb/blocks/movie-listing/actions
{
"type": "markAsBroken",
"data": {
"version": "2"
}
}
Remarks
Marking a block version as broken will disable it and ensure it can't be released
Responses
HTTP status code | Reason | Model |
---|---|---|
202 | Accepted | Block version |
401 | Unauthorized | Error |
404 | Project not found | Error |
422 | Validation error | Error |
500 | Internal server error | Error |