---
title: "GET | List all API secrets"
slug: "api-get-list-all-api-secrets"
updated: 2026-03-04T12:05:22Z
published: 2026-03-04T14:37:40Z
canonical: "docs.senhasegura.io/api-get-list-all-api-secrets"
---

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

# GET | List all API secrets

Access information of API secrets stored **MySafe**.

## Request

` GET` `api/mysafe/secretapi`

## Request parameters

Send the parameters below as **query** in the URL.

- <summary data-tomark-pass=""><code data-tomark-pass="">tag</code> - <b data-tomark-pass="">string</b> - Filters API secrets by the tag registered.</summary>
- <summary data-tomark-pass=""><code data-tomark-pass="">identifier_code</code> - <b data-tomark-pass="">string</b> - Filters API secrets by their identifier.</summary>

### Example request

` GET` `{{url}}api/mysafe/secretapi` - Lists all API secrets.

` GET` `{{url}}api/mysafe/secretapi?tag=cloud` - Lists API secret(s) registered with the `tag`= `cloud`.

` GET` `{{url}}api/mysafe/password?identifier_code=12534` - Lists API secret(s) registered with the `identifier_code`= `12534`.

## Response

```
HTTP/1.1 200 OK
```

```
{
    "code": 200,
    "response": {
        "status": 200,
        "message": "",
        "error": false,
        "error_code": 0,
        "detail": "",
        "mensagem": "",
        "erro": false,
        "cod_erro": 0
    },
    "api_secret_on_list": [
        {
            "identifier": "3",
            "name": "GCP1",
            "need_justify": "0",
            "need_approval": "0",
            "can_view": true,
            "can_write": true
        },
        {
            "identifier": "4",
            "name": "GCP",
            "need_justify": "1",
            "need_approval": "1",
            "can_view": true,
            "can_write": true
        },
        {
            "identifier": "5",
            "name": "GCP1",
            "need_justify": "0",
            "need_approval": "0",
            "can_view": true,
            "can_write": true
        }
    ]
}
```

### Reponse body fields

<summary data-tomark-pass="">• <code data-tomark-pass="">api_secret_on_list</code> - <b data-tomark-pass="">array of objects</b> - Data of the stored API secrets.</summary>

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">identifier</code> - <b data-tomark-pass="">int</b> - API secret unique identification code.</summary>

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">name</code> - <b data-tomark-pass="">string</b> - Name assigned to the API secret.</summary>

 <summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">can_view</code> - <b data-tomark-pass="">string</b> - Permission to view the API secret.</summary>

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">can_write</code> - <b data-tomark-pass="">string</b> - Permission to edit the API secret.</summary>

## Errors

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

---