Is there an Apple Notes API?

Apple Notes has no developer API in the sense the word is normally used. There is no documented framework in the SDK for reading a user's notes, no public iCloud endpoint that serves them, and nothing that can notify an external service when a note changes. Notes is one of the few first-party Apple apps with no equivalent of EventKit or Contacts' address book access.

What exists instead are three routes, all of them local to a Mac, and each with a hard limit that matters.

The Notes app ships a scripting dictionary. A script running on your Mac can ask Notes for its accounts, its folders, and the body of a note, and macOS gates that behind the Automation permission prompt you have probably seen: “X wants access to control Notes.”

This is the only supported, documented way to read note content, and it is what Margin uses. Its limits are real: it only works on macOS, it only works while the Mac is awake, and it is not fast, so anything reading a large library has to be careful to ask for what changed rather than for everything.

Shortcuts ships Notes actions on both macOS and iOS, and they are genuinely useful for one-shot jobs: grab a note, append to a note, create one from a share sheet.

What Shortcuts cannot do is watch. There is no “when a note changes” trigger on either platform, so a shortcut runs when something runs it. It also has no concept of the structure inside a note: you get text, not headings and checklists and tables that could be rebuilt as blocks somewhere else. Everything past the plain text is yours to reconstruct.

Apple Notes stores its data in a SQLite database inside a protected group container in your Library folder. It is readable in principle, and several open-source tools take this route, but it is not an API: it is an internal file format with no compatibility promise. The note bodies inside it are not plain text but a compressed, undocumented blob, and the schema is free to change in any macOS release without warning or migration path.

macOS also puts it behind Full Disk Access, which is a far broader permission than reading notes: granting it hands an app your entire disk. That is a lot of trust to ask for a feature that a documented API would cover.

This is the question behind the question, and the answer follows directly from the above. Cloud automation platforms connect services to each other over the internet. To build an Apple Notes trigger, Zapier would need somewhere to send an authenticated request and something to tell it a note had changed. Neither exists. There is no Notes web API to call, and iCloud exposes nothing for third parties to subscribe to.

So the absence isn't an oversight or a gap in their roadmap. None of them can build this integration, and no amount of waiting will change that while Apple ships no API. Any tool claiming to sync Apple Notes from the cloud is either syncing something else, or asking you to run something on a Mac and not saying so.

Every working approach to getting Apple Notes out has the same shape: something has to run on a Mac, with your permission, reading notes locally. That is the whole design space. The only real questions are whether it runs continuously or only when you launch it, whether it understands the structure inside a note or just the text, and where your notes go afterwards.

Margin is one answer to that: a small Mac app that uses the Automation permission above, rebuilds each note as native Notion blocks, and keeps the mirror current in the background. The other approaches, and where each one stops working, are worth reading first, along with what Margin doesn't do yet.

If you already know you want the sync, the step-by-step guide takes about five minutes.