---
title: "PUT | Update related user"
slug: "api-put-update-related-user"
updated: 2026-11-03T14:48:14Z
published: 2026-11-03T14:48:14Z
canonical: "docs.senhasegura.io/api-put-update-related-user"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.senhasegura.io/llms.txt
> Use this file to discover all available pages before exploring further.

# PUT | Update related user

Update a related user in **Segura™**.

## Prerequisites

- Authorization with **access** permission to the **Users** resource granted by the administrator in **A2A**.  

More information in [How to manage authorizations in A2A](/v4-2/docs/how-to-manage-authorizations-in-a2a)

## Request

` PUT` `/api/user/related`

## Request parameters

Send the parameters you want to update in the **body** of the request.

- <summary><code>id</code> - <b>int</b> - <span style="color:red">required</span> - Unique identification code of the related user.</summary>

- <summary><code>username</code> - <b>string</b> - <span style="color:red">required</span> - User identification name previously registered in Segura™.</summary>

- <summary><code>name</code> - <b>string</b> - <span style="color:red">required</span> - Name assigned to the related user being created.</summary>

### Example request

` PUT` `{{url}}/api/user/related`

```
{ 
    "id": 6,
    "username": "dleite",
    "name": "deboraleiteferreira"
}
```

## Response

```
HTTP/1.1 201 CREATED
```

```
{
    "code": 200,
    "response": {
        "status": 200,
        "message": "Related user successfully updated!",
        "error": false,
        "error_code": 0,
        "detail": "",
        "mensagem": "Related user successfully updated!",
        "erro": false,
        "cod_erro": 0
    },
    "relatedUsers": {
        "id": "6",
        "name": "deboraleiteferreira",
        "username": "dleite"
    }
}
```

## Errors

****400 - Bad Request**.**

---

**Message: "1001: Parameter 'id' was not informed!"**

**Possible cause**: the required parameter `id` of the user wasn’t informed.

**Solution**: provide the `id` of the user and resend the request.

---

**Message: "1001: Parameter 'username' was not informed!"**

**Possible cause**: the required parameter `username` Segura™ of the user wasn’t informed.

**Solution**: provide the `username` Segura™ of the user and resend the request.

---

**Message: "1001: Parameter 'name' was not informed!"**

**Possible cause**: the required parameter `name` of the user wasn’t informed.

**Solution**: provide the `name` you want to register for the user and resend the request.

---

**Message: "1005: User does not exist"**

**Possible cause**: the `username` provided hasn’t returned any user.

**Solution**: provide a valid `username` and resend the request.

---

****404 - Not Found**.**

---

**Message: "Resource sub not found"**  

**Possible cause**: the URL or requested resource isn’t correct.

**Solution**: check the URL and make sure all the parameters are correct.

---

****500 - Internal Server Error**.**

---

**Message: "Unexpected error."**  

**Possible cause**: the error is in the Segura™ server.

**Solution**: contact the support team for more information.

---

**Message: "You are not authorized to access this resource."**

**Possible cause**: you don’t have the authorization to access this resource.

**Solution**: ask the administrator to check your permission to access the **Users** resources in **A2A**.

---

****Client authentication failed**.**

---

**Message: "Client authentication failed."**

**Possible cause**: failure in your application authentication with the Segura™ server.

**Solution**: check the authentication parameters such as `Access Token URL`, `Client ID` and `Client secret` and request a new access token.

---

****Invalid signature**.**

---

**Message: "Invalid signature"**

**Possible cause**: failure in recognizing the URL of the client application.

**Solution**: check the URL of the client application and resend the request.

---

****No route matched with those values**.**

---

**Message: "No route matched with those values."**

**Possible cause**: the authorization header is missing in the API request.

**Solution**: request a new access token.

---

****Request timed out**.**

---

**Message: "Request timed out."**

**Possible cause**: the request time has expired.

**Solution**: check the connectivity between the source of the request and the Segura™ server.