# GET /api/v2/notes/{note}

Read a note

- MCP id: notes.show
- Scope: api:read:project_drive
- Scope: api:read:customer_drive
- Scope: api:read:organization_drive
- Scope: api:read:user_drive
- Permission: project_drive::access
- Rate cost: 1 unit, read bucket.
- Cache-Control: private, no-store

Returns one note in the detail view.

The summary and detail payloads are identical on this resource: the body is rendered in both, because plnnrly shows note bodies inline in its list. `notable` and `user` render as {"id": N} references until named in include. There is no soft delete: a deleted note is gone, and `trashed` is not an accepted parameter. The declared permission is `project_drive::access`; the other three drive prefixes apply by owner type, and whether you can see the parent record is what actually decides.

## Parameters
- note (integer, path): The Note's numeric id.
- view (string, optional): Which field set to render.
- X-Request-Id (header, optional): A correlation id of your own. It is recorded in our logs next to the server's request id but never returned: the response header always carries the server's id. A value that does not match the pattern is discarded silently, never rejected.
- If-None-Match (header, optional): The ETag a read is conditional on. A match is answered 304 with no body.

## Response 200
- id (integer, required): Unique identifier.
- content (html, required): Note body as rich-text HTML, sanitised on read.
- order_column (integer, required, server-assigned): Sort position within the parent record. Assigned by the server; reordering is not exposed in v2.0. Positions are not counted per parent, so the sequence is effectively creation order across the whole organisation.
- user_id (integer or null, required, server-assigned): Author of the note. Always the authenticated user at create time; `null` where the author has since been deleted.
- created_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Creation timestamp.
- updated_at (timestamp (YYYY-MM-DDThh:mm:ssZ), required): Last-write timestamp; use for incremental sync.
- notable_type (string, required): The kind of record `notable` points at; it says which branch of `notable` applies.
- notable_id (integer, required): The id of the record `notable` points at.
- notable (Ref or ProjectSummary or CustomerSummary or WorkItemSummary, required): The project, customer or work item this note is attached to.
- user (Ref or UserSummary or null, required): Author of the note.
- links (NoteLinks, required)
  - self (url, required): The canonical URI of this record.

## Errors
- 403 forbidden-by-policy | insufficient-permission | insufficient-token-scope: Forbidden.
- 304 : Not modified.
- 400 idempotency-key-required | invalid-cursor | invalid-query-parameter | malformed-request | unsupported-parameter: Bad request.
- 401 token-expired | unauthenticated: Unauthenticated.
- 404 endpoint-not-found | resource-not-found: Not found.
- 406 not-acceptable: Not acceptable.
- 429 rate-limit-exceeded: Too many requests.
- 500 internal-error: Server error.
- 503 tenant-unavailable: Service unavailable.

## Example
```bash
curl -G \
  'https://<your-url>/api/v2/notes/1' \
  --data-urlencode 'include=notable,user' \
  -H 'Authorization: Bearer <token>' \
  -H 'Accept: application/json'
```