Evernote API Overview

Evernote's API provides secure access for your trusted local or web-based applications using the same network communications that are used by Evernote's own client software.

It only takes two steps to get started with the Evernote API:

  1. Register for an API key
  2. Download the API SDK, which contains client and sample code

Documentation

Start with our API Overview, which will give you an understanding of the our API architecture.

The Thrift API Reference provides complete reference documentation for our data model and the API functions used to manipulate it.

In addition to the full web service API documented in the Thrift API Reference, we expose some functionality through pure a HTTP API. This is not intended to be an alternative to the Thrift API.

If you are building a synchronizing client that keeps a local copy of a user's entire Evernote account, you must follow our synchronization specification to ensure that you transfer data as efficiently as possible and do not overwrite user data in the event of conflicting changes.

Guidelines and Terms

Evernote's service API is provided under the terms of the Evernote API License Agreement. Please review the Evernote Branding and Trademark Usage Guidelines for information about using an Evernote trademark, including the word "Evernote" and the Evernote Elephant logo, in your application or service.

Request an API Key

Note: You do not need an API key in order to use Evernote Site Memory!

You will need an API Key to use the Evernote API. To obtain a key, please provide all of the following information.

Your contact information




Your "Organization" should be the name of the company, application or site that will be using the API key. This may be presented to users to authorize or cancel authorization for your application. If this key is for your own personal use, simply enter your name in the "Organization" field.

Application Type

We offer two types of API key that differ in how the user authenticates to our servers:

  • Web service keys use OAuth to authenticate and should be used by multi-user web applications instead of storing Evernote passwords.
  • Client keys use username and password to authenticate and can be used by desktop and mobile client applications that authenticate as a single user at a time.

Application Details

Please provide a brief overview of what you're planning to do with our API.

License Agreement

I certify that I have read and agree to the terms of the Evernote API License Agreement.