---
title: "POST | Enable password"
slug: "api-post-enable-password"
updated: 2026-03-04T12:05:21Z
published: 2026-03-04T14:37:38Z
canonical: "docs.senhasegura.io/api-post-enable-password"
---

> ## 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.

# POST | Enable password

Enable a password in **MySafe**.

## Prerequisites

- Permission to edit the API secret.
- A disabled password in **MySafe**.

## Request

` POST` `api/mysafe/password/active/[identifier]`

## Request parameters

Send the parameter below in the **path** of the URL.

- <summary data-tomark-pass=""><code data-tomark-pass="">identifier</code> - <b data-tomark-pass="">int</b> - <span style="color:red" data-tomark-pass="">required</span> - Unique identification code of the password.</summary>**Note**: this value is automatically assigned by Segura® in [POST | Create password](/v4-2/docs/api-post-create-password) and is obtained in the response to the [GET | List all passwords](/v4-2/docs/api-get-list-all-passwords).

### Example request

` POST` `{{url}}api/mysafe/password/active/10`

## Response

```
HTTP/1.1 200 OK
```

```
{
    "code": 200,
    "response": {
        "status": 200,
        "message": "Password successfully activated",
        "error": false,
        "error_code": 0,
        "detail": "",
        "mensagem": "Password successfully activated",
        "erro": false,
        "cod_erro": 0
    }
}
```

          Info

          

If the password is already active, the call will return a `200` response code with the message `Password has already been activated`..

## Errors

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

---

**Message: "1005: Password not found"**

**Possible cause**: the password wasn't found.

**Solution**: check the value for the `identifier` and resend the request.

---

**Message: "1006: User does not have access"**

**Possible cause**: user isn't allowed to access the item.

---

 

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

    

---

**Message: "Unexpected error."**

**Possible cause**: the error is on the Segura® server.

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

---

 
 

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

    

---

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

**Possible causes**: failure in your application authentication with the Segura® server or incorrect URL.

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

---

****An invalid response was received from the upstream server** .**

---

**Message: "An invalid response was received from the a seupstream server**

**Possible cause**: the upstream server may be taking too long to respond, leading to a timeout error that is interpreted as an invalid response by the proxy/gateway server.

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

---

****The upstream server is timing out**.**

---

**Message: "The upstream server is timing out"**

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

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

---