Etag in verify_crdentials.json call



I have implemented the verify_credentials endpoint from the rest api. I have received the details including the email address, but the response headers do not contain the Etag header. Is that correct? The only header which has some hash that I noticed was the x-connection-hash.

Not sure if I am missing something or is this the correct behavior?



I have found a previous post which explains the X-Connection-Hash header.

According to this post it is not an etag. Has etag been leftout of verify credentials call on purpose?