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


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 no timeframe for completion of the rollout, but at present, we are only targeting our various streaming API endpoints.

Etag in verify_crdentials.json call