canonical: https://jentic.com/apis/dev.evernote.com/evernote # Dev Evernote Evernote API Jentic publishes the only available OpenAPI specification for Evernote API, keeping it validated and agent-ready. Evernote uses a Thrift-based EDAM (Evernote Data Access and Management) protocol over HTTPS rather than a REST surface. The NoteStore service handles notes, notebooks, tags, and search; the UserStore service handles user identity and authentication. Calls are POST requests with Thrift-encoded bodies, so this OpenAPI spec captures the EDAM service endpoints and the OAuth flow - not a fine-grained per-resource REST surface. ## For AI agents Call Evernote's NoteStore and UserStore EDAM services over HTTPS to manage notes, notebooks, tags, and search via Thrift-encoded POST requests, with OAuth for authentication. ## Scope Does not expose REST resources for individual notebooks or tags - all note operations route through the NoteStore Thrift endpoint, so use this spec for EDAM service access only. ## Capabilities - Create, retrieve, and update notes through the NoteStore EDAM service - Manage notebooks and tags using NoteStore Thrift operations - Run full-text and metadata searches against the user's note corpus - Authenticate users and inspect identity via the UserStore service - Drive the OAuth flow to obtain an Evernote access token for a user - Integrate Evernote content into note-taking and knowledge-management agents ## Use cases ### Note Capture from External Tools Knowledge-management workflows pipe meeting summaries, articles, or chat highlights into Evernote so users have a single searchable archive. Calls go to POST `/edam/notestore` with a Thrift-encoded createNote payload, returning the note GUID for follow-on linking. Most teams wrap this in a thin client that handles the Thrift encoding once. Example prompt: POST `/edam/notestore` with a Thrift-encoded createNote payload containing the meeting summary and target notebook GUID, then store the returned note GUID against the meeting record. ### Cross-System Search and Recall Tools that need to surface relevant notes inside other apps call NoteStore search operations to retrieve matching notes given a query. The shape lives behind POST `/edam/notestore` with a findNotes Thrift payload. Useful for sidebar widgets in CRMs or chat tools that bring user notes alongside the active record. Example prompt: POST `/edam/notestore` with a Thrift-encoded findNotes call filtering on the customer name, then surface the top three matching notes inside the CRM contact view. ### User Authentication and Account Linking Apps that store data in a user's own Evernote account drive the OAuth flow via GET /oauth and use POST `/edam/user` to verify identity once the access token is granted. This is the gate for every per-user NoteStore call, since note operations execute against the user's account. Example prompt: Drive GET /oauth to obtain a user access token, then POST `/edam/user` to fetch the user's profile and confirm the link before allowing NoteStore calls. ### Agent-Driven Note Workflows AI agents use Evernote through Jentic to capture notes from chat or browser actions and recall them later by intent. The Evernote OAuth token sits in your Jentic One instance; agents only express intents like 'save this conversation as a note' or 'find my notes about onboarding'. Example prompt: Search Jentic for 'create an Evernote note', load the POST `/edam/notestore` createNote operation, and execute it with the note title, body, and notebook GUID. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/edam/notestore` | NoteStore EDAM service for notes, notebooks, tags, and search | | POST | `/edam/user` | UserStore EDAM service for user and authentication operations | | GET | `/oauth` | OAuth flow to obtain a user access token | ## Key resources - **NoteStore** — Notes, notebooks, tags, and search operations via EDAM - **UserStore** — User identity and authentication operations - **OAuth** — OAuth flow for obtaining a user access token ## Why Jentic - **Setup:** Wiring the Evernote API by hand means completing its OAuth flow and speaking the EDAM Thrift protocol to the NoteStore and UserStore endpoints yourself, since there are no REST resources for individual notes. Through Jentic you install once, import the Evernote API from the API Directory, connect the account once, and your agent calls it. - **Permission scoping:** Evernote routes note operations through the EDAM NoteStore and UserStore endpoints with the target passed in the request body, so you limit the agent to the operations it needs, such as service access for creating or searching notes, rather than to any single notebook. - **Credential handling:** Your Evernote OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create an Evernote note' or 'search my notes', and Jentic returns the matching EDAM operation with its input schema so the agent calls the right endpoint without learning Thrift directly. ## Related APIs - **Notion API** — Notion offers a richer block-based knowledge base with a clean REST API. - **Microsoft To Do API** — Microsoft To Do covers task and lightweight note workflows for users in the Microsoft ecosystem. - **Dropbox API** — Use Dropbox to store binary attachments referenced from Evernote notes. ## FAQ ### Why is there no official OpenAPI spec for Evernote API? Evernote does not publish an OpenAPI specification - its public API is delivered as a Thrift-based EDAM protocol. Jentic generates and maintains this OpenAPI spec so that AI agents and developers can call Evernote API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Evernote API use? Evernote uses OAuth. The flow runs via GET /oauth to obtain a user access token, which is then passed alongside subsequent NoteStore and UserStore calls. Through Jentic the access token is stored encrypted in the vault. ### Can I create notes with the Evernote API? Yes - POST `/edam/notestore` accepts a Thrift-encoded createNote payload. The body must follow the EDAM Thrift schema; calling through Jentic abstracts most of the encoding work for the agent. ### How do I search notes with the Evernote API? POST `/edam/notestore` with a Thrift-encoded findNotes payload that includes the search filter and pagination parameters. The same NoteStore endpoint handles other note, notebook, and tag operations differentiated by the Thrift method. ### What are the rate limits for the Evernote API? Evernote applies per-user rate limits and returns EDAMSystemException with a rateLimitDuration when exceeded. The OpenAPI spec does not enumerate the limits - implement backoff using the rateLimitDuration value returned on the exception. ### How do I create a note through Jentic? Search Jentic for 'create an Evernote note', load the POST `/edam/notestore` createNote operation, and execute it with the note title, body, and notebook GUID. Jentic injects the OAuth token at execution time. ### Can I limit what my agent is allowed to do with the Evernote API? Yes. Because you run Jentic One yourself, your own rules decide which Evernote operations and credentials the agent may use. Since Evernote routes work through the EDAM NoteStore and UserStore endpoints with the target passed in the request body, you can allow the agent only the operations it needs, such as creating or searching notes, rather than granting it broad access. Your OAuth token stays in your instance and is injected at execution time, so the agent never handles it directly.