Reference Guide

Signing API Requests
Importance of the Date Header
Web API Reference Guide
The value of the Date HTTP header is used as part of the request signing process to enforce the
temporary state of signed requests. For this reason, the system clock on the client and server sides must
be synchronized, up to an allowed time skew of ±30 seconds.
If the server receives an API request with a Date header value that represents more than 30 seconds of
time difference (either before or after the server clock), the request will not be accepted.
The X-Zend Signature HTTP Header
In order to send authenticated API requests you are required to send the X-Zend-Signature HTTP header
with each request. It must be in the following format:
X-Zend-Signature: ;
Where is replaced with the key name, and is replaced with the calculated
request signature.
There can be any number of whitespace characters before or after the separating semicolon.
Example:
X-Zend-Signature: Arch Stanton;
a0f9b1d61e21e796d78dccdf1352f23cd328...
Note:
The signature is expected to be 64 characters long, and is cut here for readability purposes.
339