Overview

NOTE: Using ClickBank's APIs may require a rudimentary understanding of computer programming. If you do not feel equipped to proceed, we encourage you to seek assistance from someone who has computer programming experience.

ClickBank’s API methods are secure and will return a 403 [Forbidden] status code if accessed without the right credentials. To provide these credentials and access the ClickBank APIs, you must use an authorization header. This header must contain an API created from within your primary account.

Related: How to Create ClickBank API Keys

NOTE: ClickBank APIs no longer require the use of a Developer API Key.

Below find the following ClickBank API Specifications:

To access the APIs, you provide your ClickBank API Key in the authorization parameter. The authorization parameter uses the following format:

For example:

Related: How to Create a ClickBank API Key
​
​

For some programming languages, the ClickBank APIs require your system to possess a certificate for the following domain:

*.clickbank.com

Verify that you have a certificate for this domain. The procedure for acquiring this certificate varies based on your browser, but your browser indicates a secure connection to the API pages above if the certificate is present.
​
​

The ClickBank APIs are based on JSR-311 – the Java API for RESTful Web Services. The services are HTTP-based and implementation-agnostic, meaning that any web client (.NET, PHP, Java, Python, Ruby, etc.) can use them.
​
​

The ClickBank API header consists of security, output, and page parameters. The ClickBank APIs only accept query parameters; requests using form-based (post) parameters are ignored.

The HTTP specification limits a URL to 2,000 characters or fewer. Ensure that your ClickBank API URLs don’t exceed 2,000 characters.
​
​

The ClickBank APIs support the following output formats:

You select an output format by including an Accept parameter in the HTTP header.

For example, this header requests XML output:

The ClickBank APIs return the first 100 rows of data for any service call. If a request would contain more than 100 rows of data, the API returns the first 100 rows with a status code of 206 [Partial Content]. To retrieve the additional pages, include a Page parameter in the HTTP header indicating which pages to retrieve.

For example, this header requests page 3:

Once the final page has been accessed, the service returns a status code of 200 [OK] instead of 206 [Partial Content].

To protect the ClickBank API system, quotas are placed on ClickBank API usage.

The default quotas are:

If a quota is exceeded, the ClickBank API will return a status code of 403 [Forbidden] and a message indicating that the quota has been met.