Mobile Integration Overview

Evernote provides a web application that's tailored for mobile devices. Here you'll find information on how to integrate with this application.

Authentication

For seamless integration with the Evernote mobile web application, an authentication token must first be obtained. Typically a thick client application will store Evernote credentials (username and password) that can be used to obtain a valid authentication token from the Evernote service. See the API documentation on how to obtain an authentication token.

Once the token is obtained it can be used to access the Evernote mobile web application via the following URL:

If the required authentication token is missing or invalid, the Evernote web application will prompt for username and password. To force that behavior, use the login action:

• 
• 

Client identification

Evernote encourages all third-party developers to includes a client identifier string when making requests to the Evernote mobile web application. The format of the client identifier string is as follows:

Only the Application portion is required when making requests. The following is a list of valid identifiers:

• Evernote Integrated App/1.0
• Evernote Integrated App/1.0; AcmeOS/1.0; AcmeHandhelds/Anvil-1.0

The client identifier should be included in all HTTP requests by appending device query parameter with the URL-encoded client identifier string:

Together, the auth token and the client identifier string should be included in all requests made to the Evernote mobile web application.

Geolocation

The Evernote mobile web application provides ability to search for notes near a geolocation. However, that information must be provided by including lat and lng query parameters specifying latitude and longitude of the current location:

• 
• 

Geolocation parameters are optional and can be combined with any request to the Evernote mobile web application.

Alternative interfaces

The Evernote mobile web application can be viewed using either plain or dynamic interfaces. The plain interface targets a larger variety of mobile devices and has a simplistic navigational design. The dynamic interface targets higher-end devices with browsers supporting Javascript, and with touch navigation in mind. Evernote attempts to deduce what type of interface to use based on the incoming HTTP requests. However, that does not guarantee a perfect match. To specify which interface to use, simply include if query parameter:

For plain interface:

For dynamic interface:

Choice of interface can be combined with any request to the Evernote mobile web application.

Browsing notes

After authentication, the Evernote web application directs user to the note browser. The browser can always be accessed by this URL:

• 
• 

Viewing settings

To view user's settings, use the settings action:

• 
•