If, like me, you are still persisting with Evernote’s aging API (I have two projects that use it) you will have come across the Auth Token that is used to validate requests. In today’s post we are going to try and unpack that.
What does it contain?
The raw Auth Token looks like this:
S=s3:U=13d80:E=1a4b63e2798:C=19d5e8cfb98:P=185:A=application-id:V=2:H=a3b92abc123567d7a6ec10b23cad2dfc
Which breaks down into eight parts as follows:
S=s3
U=13d80
E=1a4b63e2798
C=19d5e8cfb98
P=185
A=application-id
V=2
H=a3b92abc123567d7a6ec10b23cad2dfc
What each part means
S=s3
- Shard ID – Tells Evernote which backend cluster your account lives on.
U=13d80
- User ID (in hex) – Internal Evernote user identifier
E=1a4b63e2798
- Expiry










