Skip to content

API reference

Get note

customers.GetNoteReadAPI key

Read a note by ID. Returns item: null when no visible record matches.

POST/v1/operations/customers.GetNote
On this page

Access & visibility

Allow customers.GetNote on your API key. Resource read permissions: core:Note.

Workspace access by default. Private member data requires approved member delegation through Brigg-Act-As; the key supplies permissions while private ownership and project boundaries remain enforced.

Set up authentication · Choose permissions

Request fields

Send a JSON object with the following fields. Required fields must be included; omit optional fields you do not need.

idstringRequired

ID of a visible core:Note record. Find it with customers.ListNotes. Use the record's top-level id, not a business field or account ID.

Response

Returns 200 OK with a JSON body.

item: null means there is no matching record visible to this caller. It does not reveal whether an inaccessible record exists.

Record metadata sits outside data. Timestamps created_at and updated_at are Unix milliseconds. Optional business fields may be absent; absence does not mean false or zero. A field accepts null only when its type includes null.

itemNoteRecordRequired

null when no such record

NoteRecord
idstringRequired

Stable core:Note record ID. Keep this top-level value when reading or referring to this record. Available actions are linked under Next steps; an ID does not imply the resource can be edited.

created_atnumberRequired

Time the record was created, in Unix milliseconds.

updated_atnumberRequired

Time the record most recently changed, in Unix milliseconds. Use with overlapping windows for incremental reads.

created_bystring or nullRequired

Account that originally created the record, or null for a workspace/system-originated record. This is provenance, not its current owner or a Person record ID.

privatebooleanRequired

True for a member-owned private record. An API key needs approved delegation to that owner; false alone does not bypass resource grants or other access rules.

dataNoteRequired

The record's fields.

Note
Note2 fields
bodystringRequired

Customer activity note content, which may contain Markdown. Preserve the text and render it safely; this is not HTML.

occurred_atstringOptional

Date of the activity described by the note, in YYYY-MM-DD format. Creation time is recorded separately.

Related record and author3 fields
parent_typestringOptional

CRM parent type: core:Company, core:Person or core:Deal. Pair with parent_id. These resource identifiers differ from public operation namespaces.

parent_idstringOptional

Record ID within parent_type. The type and ID must identify the same parent.

author_refstringOptional

Person record representing the note's author, not the author's account ID. Brigg supplies the acting member's Person reference on creation when omitted.

Errors & retries

This operation reads data. It needs no idempotency key and can be retried after a transient failure.

For rate limits, follow the server’s retry guidance and back off. See HTTP errors and safe retries and limits.

HTTP status Code What to do
400 invalid_json Send a JSON object with Content-Type: application/json.
400 invalid_input Check the request fields and types.
401 invalid_key The workspace API key is missing, invalid or revoked.
403 forbidden Check the key’s operation and resource grants. If Brigg-Act-As is supplied, the key must be authorized to delegate to that member.
404 not_found The requested operation or resource is not available to this credential.
429 rate_limited Wait for Retry-After before retrying.

Next steps

Download OpenAPI · Versioning & retirement

JSON schemas

Use the complete schemas for validation or client generation.

Full request JSON schema
{
  "type": "object",
  "properties": {
    "id": {
      "type": "string",
      "description": "ID of a visible `core:Note` record. Find it with [customers.ListNotes](/developers/reference/customers/ListNotes). Use the record's top-level `id`, not a business field or account ID."
    }
  },
  "required": [
    "id"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "id": "e_note_example"
    }
  ]
}
Full response JSON schema
{
  "type": "object",
  "properties": {
    "item": {
      "type": [
        "object",
        "null"
      ],
      "properties": {
        "id": {
          "type": "string",
          "description": "Stable core:Note record ID. Keep this top-level value when reading or referring to this record. Available actions are linked under Next steps; an ID does not imply the resource can be edited."
        },
        "created_at": {
          "type": "number",
          "description": "Time the record was created, in Unix milliseconds."
        },
        "updated_at": {
          "type": "number",
          "description": "Time the record most recently changed, in Unix milliseconds. Use with overlapping windows for incremental reads."
        },
        "created_by": {
          "type": [
            "string",
            "null"
          ],
          "description": "Account that originally created the record, or null for a workspace/system-originated record. This is provenance, not its current owner or a Person record ID."
        },
        "private": {
          "type": "boolean",
          "description": "True for a member-owned private record. An API key needs approved delegation to that owner; false alone does not bypass resource grants or other access rules."
        },
        "data": {
          "type": "object",
          "properties": {
            "body": {
              "type": "string",
              "description": "Customer activity note content, which may contain Markdown. Preserve the text and render it safely; this is not HTML."
            },
            "occurred_at": {
              "type": "string",
              "description": "Date of the activity described by the note, in YYYY-MM-DD format. Creation time is recorded separately."
            },
            "parent_type": {
              "type": "string",
              "description": "CRM parent type: core:Company, core:Person or core:Deal. Pair with parent_id. These resource identifiers differ from public operation namespaces."
            },
            "parent_id": {
              "type": "string",
              "description": "Record ID within parent_type. The type and ID must identify the same parent."
            },
            "author_ref": {
              "type": "string",
              "description": "Person record representing the note's author, not the author's account ID. Brigg supplies the acting member's Person reference on creation when omitted."
            }
          },
          "required": [
            "body"
          ],
          "additionalProperties": false,
          "description": "The record's fields.",
          "title": "Note"
        }
      },
      "required": [
        "id",
        "created_at",
        "updated_at",
        "created_by",
        "private",
        "data"
      ],
      "additionalProperties": false,
      "description": "null when no such record",
      "title": "NoteRecord"
    }
  },
  "required": [
    "item"
  ],
  "additionalProperties": false,
  "examples": [
    {
      "item": {
        "id": "e_note_example",
        "created_at": 1791276900000,
        "updated_at": 1791280800000,
        "created_by": "a_jamie",
        "private": false,
        "data": {
          "body": "Alex confirmed that the pilot will start on 19 October.",
          "occurred_at": "2026-10-06",
          "parent_type": "core:Company",
          "parent_id": "e_company_northstar"
        }
      }
    }
  ]
}

Search by operation name or what you want to build.

Use arrow keys to browse. Enter opens a result.