Etag in verify_crdentials.json call

nakulbali · 2016-01-02T15:29:24.702Z

Hi,

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?

Regards,
Nakul

nakulbali · 2016-01-02T17:50:23.769Z

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

X-Connection-Hash to replace X-Transaction header for debugging Streaming APIs

You may already be familiar with the X-Transaction header that we pass with API responses to give you a unique identifier for debugging. Starting as early as April 8, you will begin seeing a new header, X-Connection-Hash, which supersedes the X-Transaction header. When reporting an issue in our forums, you should always provide the raw HTTP request and response (including all headers), but it will be particularly helpful to include the X-Connection-Hash header value. At present, there is n…

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