# 4.53. Organisation Approver - Approve deleted block request for organisation

<table border="1" id="bkmrk-id-4.1.-description-" style="border-collapse: collapse; width: 100%; height: 347px;"><colgroup><col style="width: 50%;"></col><col style="width: 50%;"></col></colgroup><tbody><tr style="height: 29px;"><td style="height: 29px;">**Id**</td><td style="height: 29px;">4.53.</td></tr><tr style="height: 125px;"><td style="height: 125px;">**Description**</td><td style="height: 125px;">As an **<span class="notion-enable-hover" data-token-index="1">Organisation Approver</span>**,

I need to be able to approve block deletion requests from <span class="notion-enable-hover" data-token-index="3">Editors</span> linked to my Organisation,

So that I can guarantee that no block is deleted by mistake and to preserve the quality and reliability of the register

</td></tr><tr style="height: 29px;"><td style="height: 29px;">**Priority**</td><td style="height: 29px;"><span style="color: rgb(230, 126, 35);">**Medium**</span></td></tr><tr style="height: 29px;"><td style="height: 29px;">**Actors**</td><td style="height: 29px;">Organisation Approver</td></tr><tr style="height: 77px;"><td style="height: 77px;">**API Calls**</td><td style="height: 77px;">**POST** /blocks/&lt;block-id&gt;/approve

**POST** /blocks/&lt;block-id&gt;/reject

**PUT** /blocks/&lt;block-id&gt;

**PATCH** /blocks/&lt;block-id&gt;

</td></tr><tr style="height: 29px;"><td style="height: 29px;">**Linked Processes**</td><td style="height: 29px;">[7.8. Approve delete block request](https://doc.rncv.lu/books/architecture-documentation/page/78-approve-delete-block-request "7.8. Approve delete block request")

</td></tr><tr style="height: 29px;"><td style="height: 29px;">**Status**</td><td style="height: 29px;">**<span style="color: rgb(22, 145, 121);">Implemented</span>**</td></tr></tbody></table>

### Preconditions

1. The User must be authenticated and have the **Organisation** **Approver** role.
2. The User has a valid block ID that is marked as “to be deleted”
3. The delete request has been performed by a user from the Approver’s organisation.

### Postconditions

1. The system returns a confirmation that the decision (validation/rejection) has successfully been applied

### Main flow

1. The **Organisation** **Approver** uses an API call to approve/reject the block deletion by ID (POST).
2. The system validates the deletion request.
3. The system returns the confirmation that the request has been approved/rejected

### Exceptions

#### \[400 Bad Request\] Invalid input:

If mandatory fields are missing or invalid, the system returns an error message.

#### \[404 Not Found\] Block not found

Error returned by the system if the block is not found.

#### \[500 Internal Server Error\] System Error

If the system fails to save changes due to an internal error, it displays an appropriate message and logs the error for further investigation.