CallNote API

The CallNote API lets you push transcripts in and pull notes out. Send a transcript your call system produced and CallNote generates a structured note from it; or fetch your lodged notes into a Zap, a Make scenario, a data warehouse, or your own code. Authenticate with an API key on every request.

Authentication

Every request needs an API key. To create one:

1. Log in to CallNote and go to Integrations.
2. On the API / Zapier card, click Generate API key and give it a label.
3. Copy the key straight away - it is shown once and starts with cn_live_.

Send the key on every request as either of these headers:

Authorization: Bearer cn_live_xxxxxxxxxxxxxxxxxxxx
X-API-Key: cn_live_xxxxxxxxxxxxxxxxxxxx

Treat the key like a password. It grants read access to your organisation's notes. If a key is exposed, revoke it on the same Integrations page and generate a new one.

Base URL

https://callnote.com.au/api/zapier

GET /me

Verifies your API key and returns your organisation name. Use it to test a key.

curl https://callnote.com.au/api/zapier/me \
  -H "Authorization: Bearer cn_live_xxxxxxxxxxxxxxxxxxxx"

Response:

{ "organisation": "Your brokerage" }

GET /notes

Returns your notes, newest first, as a JSON array. This is the endpoint a “new note” automation polls.

curl "https://callnote.com.au/api/zapier/notes?limit=10" \
  -H "Authorization: Bearer cn_live_xxxxxxxxxxxxxxxxxxxx"

Response - an array of note objects:

[
  {
    "id": "9acd5d0b-93e5-46d3-83c0-3681a9681751",
    "title": "First home buyer borrowing capacity",
    "client_name": "Sarah Nguyen",
    "client_email": "sarah@example.com",
    "template": "Loan Suitability",
    "note_text": "SUMMARY\nFirst home buyer, budget ~$650k...",
    "lodged_at": "2026-07-18T04:12:55.000Z",
    "url": "https://callnote.com.au/calls/be58e093/note"
  }
]

note_text is the full note as plain text. client_name, client_email and template can be null when the note has no linked client or template.

POST /notes

Create a note from a transcript. Send the transcript your call system produced and CallNote generates a structured note from it, then returns the finished note. It lands in your library as a draft for a broker to review and lodge - the same review-and-lodge step as every other source, so nothing about compliance changes.

curl -X POST https://callnote.com.au/api/zapier/notes \
  -H "Authorization: Bearer cn_live_xxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json" \
  -d '{
    "transcript": "Broker: Thanks for jumping on. Client: No worries...",
    "client_name": "Sarah Nguyen",
    "external_id": "your-call-id-123"
  }'

Returns 201 with the created note (the same shape as above, with "status": "draft"). Generation takes a few seconds; the request stays open until the note is ready. A repeat with the same external_id returns 200 with "idempotent": true.

Errors

Errors return a JSON body with an error message and the matching HTTP status:

Notes on scope

You can create notes from transcripts and read your notes. What the API deliberately does not do is edit or delete a note that has already been lodged - a lodged note is sealed and audit-logged, and changing it out of band would undermine exactly that. Changes to lodged notes stay as append-only amendments inside CallNote. If you need something else, tell us what you are building.