/edam/* → endpoint removal
Evernote API
Deprecated, no date
The classic Evernote Developer API and its SDKs are deprecated without a shutdown date. Calls to /edam/* are no longer actively developed, though they remain available so existing integrations can be maintained. Requests eventually face removal where calls fail, but no effective date has been set.
Calls it hits
/edam/*
What to use instead of these calls
Keep existing EDAM integrations as they are, since Evernote names no replacement API. Because no replacement exists for the classic API, whether to continue depending on it is a product decision.
Evernote names no replacement for the classic API: whether to keep depending on it is a product decision.
In Evernote API's words
The classic Evernote Developer API (EDAM) and its SDKs are deprecated and no longer actively developed. They remain available here so you can maintain existing integrations.
Facts
- API
- Evernote API
www.evernote.com - Kind
- Endpoint removal
- Takes effect
- No date given yet
- Calls after that day
- Fail
- Source
- Announcement
- Last updated
- Verified
- , against Evernote API's own pages
Questions
When does this change take effect?
Evernote API deprecated /edam/* without giving a shutdown date yet.
Do these calls still work?
Yes, they still work: Evernote API has not given a shutdown date yet.
How do I find the calls this hits in my code?
Okapi reads your repository, finds the calls this change hits and opens a pull request with the fix. It never commits to your branches: every change comes as a pull request you review.
More from Evernote API 1
-
No date
/shard/*Endpoint removal Deprecated, no date
Is your code calling this?
Okapi finds the calls this change hits in your repo and opens the pull request with the fix.