Every request to the API needs to be authenticated using a signature in the HTTP headers. A good place to start when building out your request signing logic is the List Services API.


API accounts will be given a key pair consisting of an Access Key ID (like ‘qzwBzqCiMsuHoUrZEcLq’) and a Secret Access Key (like ‘znkcyBjEWKQFIELAkotspHDoJbwHJyRPXChFYWDn’).  These keys will be used to sign every request.  Keys are tied to a merchant account.


The API requires that the client send the following headers. All required x-lod-* headers are used to compute authorization.

  • authorization: contains authorization components as described below
  • accept: in this version we will only be supporting XML.  Anything other than “text/xml” will result in a Bad Request error.
  • x-lod-timestamp: UNIX timestamp
  • x-lod-version: version of the API. We will use date strings to label versions. For example: 2014-03-18
  • Content-Type should be “text/xml”. Often this will default on GET requests. Depending on what libraries you use, you might need to explicitly set Content-Type on POSTs or force it by submitting an empty string in the body if no body is required. Please note: the Add File API requires you to set the Content-Type to the mime-type of the file you are uploading.

Authorization Header

An example POST against the resource /api/project might have an authorization header like

Authorization: LOD1-BASE64-SHA256

Note that there is space between the first two components, LOD1-BASE64-SHA256 and KeyID, and that the subsequent components, KeyID, Signature, and SignedHeaders are separated by a comma.

The following table describes the various components of the Authorization header value.

Component Description

The algorithm that was used to

calculate the signature.

The string specifies LOD Signature

Version 1 (LOD1) and the signing

algorithm (BASE64-SHA256).

A valid Access Key ID.

A signature in the form of




secret key:





See example below


A semicolon-separated list of

request headers used to compute

Signature. The list includes header

names only. The required x-lod-*

headers must be first and in

alphabetical order. For example,



The best place to start when learning how to develop a valid request signature is the List Services API. In this case, the string to encrypt for the signature is:



  • GET is the HTTP method you used
  • /api/services is the resource you are calling. This is the URL path without any querystring arguments. If the URL uses a querystring argument, such as the “extension” filter in the List Services API, you must leave out the query string.
  • AAA...AAA is your secret key
  • 2014-02-21T17:49:24.655024 is the current time stamp. This needs to be the same as x-lod-timestamp. Note, you must use a 24 hour clock.
  • 2014-02-28 is the version of the API you are using. This needs to be the same as x-lod-version.
  • text/xml is what you passed in the accept header