GoliathDevelopersGet an API key
Reference/Contactsgenerated from the gateway manifest

editContactNote

Rewrite an existing note's body (by noteId).

POST/api/v1/callWRITEidempotent · 24 hruns as the key's owner
View as Markdown

Rewrite an existing note's body (by noteId). REVERSIBLE: the note keeps its id and timeline position, so a wrong edit can be edited again, and no permission is needed when the user asked for a correction. Pass the FULL replacement body: it replaces the text, it does not append. noteIds come from getContact (notes[]) or a NOTE entry's note payload in listContactActivities; addContactNote returns none, so re-read the contact for the note you just wrote. The response echoes the saved body and updatedAt plus the owning contact (id + name): quote the corrected text back rather than assume it took. Only a note the key owner wrote, unless they are a team admin; a note whose author.kind is AI is someone else's, so a NON-ADMIN key is refused on one: check the author before offering to correct a note.

curl https://server.goliathdata.com/api/v1/call \
  -H "Authorization: Bearer $GOLIATH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "operationId": "editContactNote",
    "variables": {
      "noteId": "<noteId>",
      "body": "<String>"
    }
  }'
import { GoliathClient } from '@goliath-data/sdk'

const goliath = new GoliathClient({
  apiKey: process.env.GOLIATH_API_KEY!,
  baseUrl: 'https://server.goliathdata.com',
})

const result = await goliath.contacts.editContactNote(
  {
    noteId: '<noteId>',
    body: '<String>'
  },
  { idempotencyKey: crypto.randomUUID() },
)
const res = await fetch('https://server.goliathdata.com/api/v1/call', {
  method: 'POST',
  headers: {
    Authorization: `Bearer ${process.env.GOLIATH_API_KEY}`,
    'Content-Type': 'application/json',
    'Idempotency-Key': crypto.randomUUID(),
  },
  body: JSON.stringify({
    operationId: 'editContactNote',
    variables: {
      noteId: '<noteId>',
      body: '<String>'
    }
  }),
})
const { data, errors } = await res.json()

Variables

The example sends only what the schema requires. Some operations also need one of several optional variables (one filter or another, say); the description above says which.

noteIdID!required
bodyString!required

Response

What comes back under data: a list shows as one entry, and a value as its type.

response shape
{
  "data": {
    "noteMutation": {
      "editNote": {
        "id": "<ID>",
        "body": "…",
        "updatedAt": "2026-01-01T00:00:00.000Z",
        "contact": {
          "id": "<ID>",
          "name": "…"
        }
      }
    }
  }
}

Errors

400unknown_variable

A variable the operation does not declare. A typo is refused rather than silently dropped.

401unauthorized

No bearer header, or the key is invalid or revoked.

403insufficient_scope

The key lacks the scope the operation requires.

403forbidden

A referenced record does not exist, was deleted, or is outside your organization. The gateway cannot tell those apart.

409idempotency_conflict

A request with this Idempotency-Key is still in flight.

Idempotency

Send an Idempotency-Key of 1 to 255 characters. A finished request retried with the same key replays its stored response, marked Idempotency-Replayed: true; one still in flight returns 409 idempotency_conflict. Keys expire after 24 hours. Write without fear →

READgetContactREADgetContactsPropertiesREADfindContactsByNoteREADsearchInteractionsREADcountContactsREADfindContacts