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

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

Access information of notes stored in **MySafe**.

## Request

` GET` `api/mysafe/note`

## Query parameters

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

- <summary data-tomark-pass=""><code data-tomark-pass="">tag</code> - <b data-tomark-pass="">string</b> - Filter notes by tags.</summary>
- <summary data-tomark-pass=""><code data-tomark-pass="">name</code> - <b data-tomark-pass="">string</b> -Filters notes by name.</summary>

### Example requests

` GET` `{{url}}api/mysafe/note` - Gets all notes.

` GET` `{{url}}api/mysafe/note?tag=secret` - Gets the note(s) registered with the `tag` = `secret`.

` GET` `{{url}}api/mysafe/note?name=secret note` - Gets the note(s) registered with the `name` = `secret note`.

## Response

```
HTTP/1.1 200 OK
```

```
{
    "code": 200,
    "response": {
        "status": 200,
        "message": "",
        "error": false,
        "error_code": 0,
        "detail": "",
        "mensagem": "",
        "erro": false,
        "cod_erro": 0
    },
    "note_on_list": [
        {
            "identifier": "1",
            "name": "My note",
            "tags": "",
            "need_justify": "0",
            "need_approval": "0",
            "can_view": true,
            "can_write": true
        },
        {
            "identifier": "2",
            "name": "Secret note",
            "tags": "secret",
            "need_justify": "0",
            "need_approval": "0",
            "can_view": true,
            "can_write": true
        },
        {
            "identifier": "6",
            "name": "Staff meeting decisions",
            "tags": "meeting",
            "need_justify": "0",
            "need_approval": "0",
            "can_view": true,
            "can_write": true
        },
        {
            "identifier": "9",
            "name": "TC Meeting",
            "tags": "API, MySafe, TC",
            "need_justify": "0",
            "need_approval": "0",
            "can_view": true,
            "can_write": true
        }
     ]
}
```

### Response body fields

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

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

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">name</code> - <b data-tomark-pass="">string</b> - Note name.</summary>

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">tags</code> - <b data-tomark-pass="">string</b> - Keywords associated with the note.</summary>

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

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">can_write</code> - <b data-tomark-pass="">string</b> - Permission to edit the note.</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's 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 upstream server."**

**Possible cause**: the upstream server may be taking too long to respond, leading to a timeout error interpreted as an invalid response by the proxy/gateway server. **Solution**: check the connectivity between the request origin and the Segura® server.

---

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

---

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

**Possible cause**: the request timed out. **Solution**: check the connectivity between the request origin and the Segura® server.

---