Fetch Single Note

Retrieve a single note by its NoteToken. The note content is automatically decrypted before being returned.

POST /notes/single

Description

This endpoint retrieves a single note owned by the authenticated user. The note is identified by its NoteToken and can only be fetched by the user who created it. The Note field is automatically decrypted before being returned.

Authentication

This endpoint requires Bearer token authentication via the Authorization header.

Request Body

Field Type Required Description
NoteToken String Yes Unique identifier of the note to retrieve (UUID v4)

Code Examples

curl -X POST "https://api-v3.sweeppea.com/notes/single" \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"NoteToken":"uuid-v4-string"}'

Response

200 OK

{ "Response": true, "Data": { "_id": "68df07e9896a685bf51d58cf", "NoteToken": "uuid-v4-string", "Title": "Example Note", "Note": "Decrypted note content", "Views": 0, "Pinned": false, "Status": false, "CreatedByAdmin": false, "CreationDate": "2025-10-02T23:16:57.491Z" } }

Error Responses

400 Bad Request

{ "Response": false, "Message": "NoteToken is Required", "Code": 400 }

401 Unauthorized

{ "Response": false, "Message": "Invalid or Missing Bearer Token", "Code": 401 }

403 Forbidden

{ "Response": false, "Message": "Invalid API Token", "Code": 403 }

404 Not Found

{ "Response": false, "Message": "Note Not Found", "Code": 404 }

500 Internal Server Error

{ "Response": false, "Message": "Internal Server Error", "Code": 500 }

Important Notes

  • 🔒 Ownership Verification: Users can only fetch notes they own
  • 🔓 Auto Decryption: The Note field is stored encrypted and automatically decrypted in the response
  • 🆔 Note Identification: Notes are identified by their unique NoteToken (UUID v4)
  • 🔍 Not Found: Returns 404 if the note doesn't exist or belongs to another user