This repository has been archived by the owner on Apr 25, 2024. It is now read-only.
Updated readme on obtaining developer tokens #116
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
As seen on #89, developer tokens are harder to get that one expects, and they must be converted to user tokens. As normal login via oauth is currently disabled, this is the only way to login and it requires a complex process. This commit documents the process referring to the FAQ in a step-by-step manner.
iafan
reviewed
May 30, 2019
|
|
||
| Finally, you will receive another email from devsupport (check on your spam | ||
| folder) notifying that your key has been activated on production servers. | ||
| It will contain a link to get a [personal token](https://dev.evernote.com/get-token/) from that key that you can use as |
There was a problem hiding this comment.
Please replace this paragraph with "Once your API key activation is processed by Evernote Developer Support, they will send you an email with further instructions on obtaining the personal token."
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As seen on #89, developer tokens are harder to get that one expects, and they
must be converted to user tokens.
As normal login via oauth is currently disabled, this is the only way to login
and it requires a complex process. This commit documents the process referring
to the FAQ in a step-by-step manner.