# 4.51. Approver - Approve or reject update vertical cabling request

<table border="1" id="bkmrk-id-4.1.-description-" style="border-collapse: collapse; width: 100%; height: 268px;"><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.51.</td></tr><tr style="height: 94px;"><td style="height: 94px;">**Description**</td><td style="height: 94px;">As an<span class="notion-enable-hover" data-token-index="1"> **Approver**</span>,

I need to be able to approve an update vertical cabling request

So that I can guarantee that the data updates performed on the registry are accurate and meet the needed data quality standards.

</td></tr><tr style="height: 29px;"><td style="height: 29px;">**Priority**</td><td style="height: 29px;">**<span style="color: rgb(224, 62, 45);">High</span>**</td></tr><tr style="height: 29px;"><td style="height: 29px;">**Actors**</td><td style="height: 29px;">Approver</td></tr><tr style="height: 29px;"><td style="height: 29px;">**API Calls**</td><td style="height: 29px;">**GET** /physical-links

**POST** /physical-links/&lt;physical-link-id&gt;/approve

**POST** /physical-links/&lt;physical-link-id&gt;/reject

**PUT** /physical-links/&lt;physical-link-id&gt;

**PATCH** /physical-links/&lt;physical-link-id&gt;

</td></tr><tr style="height: 29px;"><td style="height: 29px;">**Linked Processes**</td><td style="height: 29px;">[7.6. Approve update vertical cabling request](https://doc.rncv.lu/books/architecture-documentation/page/76-approve-update-vertical-cabling-request "7.6. Approve update vertical cabling 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 **Approver** role.
2. The User has a valid Physical Link ID that has to be validated

### Postconditions

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

### Main flow

1. The **Approver** retrieves the list of physical links to be approved (GET)
2. The **Approver** can perform amendments if needed prior to the approval
3. The **Approver** uses an API call to approve/reject the physical link by ID (POST).
4. The System validates the approval request.
5. 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\] Physical link not found

Error returned by the system if the physical link 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.