Quicklizard Legacy API - Introduction

This API provides endpoints to read available and accepted price recommendations, and create and update products on our platform.

API base URI

API calls should be made to https://api.quicklizard.com

Authentication

Each request made to our API must be signed using an API key/secret pair we provide you. You may access your API key/secret pair from our online application by logging in and visiting the "Client Configuration" page available from the top drop-down menu

Accounts with Multiple Stores

Some accounts on Quicklizard have multiple stores, each with its own client key and API key/secret pair.

The client key is used in our SDK to send click-stream analytics to our platform. The corresponding API key/secret pair is used to identify which store you wish to work against when making API calls.

In case your account has more than one store, please adjust your workflow to make sure calls to our API are done using the correct API key/secret pair which corresponds to the store's data you wish to work with.

Time-stamping

Each request must also be time-stamped by passing an additional query-string parameter named qts which contains a UTC Unix timestamp in milliseconds.

Time-stamping the request ensures your API calls are protected against request replay attacks, and is therefore mandatory.

Important!

Timestamps must be in milliseconds rather than seconds and must be computed in UTC rather than local time-zone.

Error Handling & Debugging

500 HTTP errors must be handled by you to ensure smooth operation in case of unforeseen issue with sending or reading data using our API.

Whenever possible, 500 errors will be accompanied by an error text that explains what went wrong.

To ensure you're able to quickly identify and handle any technical problems that arise during initial API integration, and later on when your platform is already integrated with QL, please be sure to go over the Debugging section.

In addition, we highly recommend that you set up detailed logging of your API calls, that'll make it easier for you to pin-point problems, and raise them with our support team if needed.

At the very least your logs should include the following:

  • API request URL and HTTP method
  • API request payload for POST / PUT requests
  • HTTP request headers
  • API response