---
title: "GET | List a note by [identifier]"
slug: "api-get-list-a-note"
updated: 2026-03-04T12:05:22Z
published: 2026-03-04T14:37:38Z
canonical: "docs.senhasegura.io/api-get-list-a-note"
---

> ## 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 a note by [identifier]

Access a note information in **MySafe**.

## Request

` GET` `api/mysafe/note/[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> - Note unique identification code.</summary>
**Note**: this value is automatically assigned by Segura® in [POST | Create note](/v4-2/docs/api-post-create-note) and is obtained in the response to the [GET | List all notes](/v4-2/docs/api-get-list-all-notes) request.

### Example request

`GET` `{{url}}api/mysafe/note/2`

## Response

```
HTTP/1.1 200 OK
```

```
{
    "code": 200,
    "response": {
        "status": 200,
        "message": "Success",
        "error": false,
        "error_code": 0,
        "detail": "",
        "mensagem": "Success",
        "erro": false,
        "cod_erro": 0
    },
    "note_entity": {
        "identifier": "2",
        "name": "Secret note",
        "note": "My top secret note",
        "tags": "secret",
        "users_allowed": [],
        "groups_allowed": []
    }
}
```

### Response body fields

<summary data-tomark-pass="">• <code data-tomark-pass="">notes_entity</code> - <b data-tomark-pass="">object</b> - Data of the stored note.</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="">users_allowed</code> - <b data-tomark-pass="">array of objects</b> - List of users' names and permissions to view and/or edit the note.</summary>

<summary data-tomark-pass="">&nbsp;  &nbsp;→ <code data-tomark-pass="">groups_allowed</code> - <b data-tomark-pass="">array of objects</b> - List of groups' names and permissions to view and/or edit the note.</summary>

## Errors

****400 - Bad request**.**

---

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

**Possible cause**: user doesn't have access to this note.

---

**Message: "1010: Unexpected identifier type"**

**Possible cause**: URL not recognized. **Solution**: check the URL and resend the request .

---

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

---