Leankr API key request

You will get access to the Leankr API for 3 months, free of charge.

Limited to one API key per company.

Please send an email to contact@leankr.com if you want to extend the 3-month evaluation period.


mandatory fields

You will receive an email with your personal Leankr API key.
Briefly describe your application
Type the captcha here

CAPTCHA Image

Subscribe to Leankr developer API



General Concepts


Authentification

Every GET request must include a parameter called “api_key” with your granted key as value. Non-authenticated requests will be answered by a HTTP 401 response code as follows:

{ "errorCode": 401, "errorMsg": "401 Unauthorized", "detailedMsg": "Application not authorized" }

Rate Limitations

The REST API has a rate limitation policy based on 15 minutes slot.
The rate limit is set to 100 requests per slot.
Whenever this rate is exceeded, the request will response a HTTP 401 code with a JSON encoded message as follows:

{ "errorCode": 401, "errorMsg": "401 Unauthorized", "detailedMsg": "Rate limit exceeded (190 / 180)" }

The count will be reset to 0 once the current time slot is over.
If you think your particular usage of the API requires a higher rate, do not hesitate to contact us.
You may also consider using our PUSH API to get rid of this limitation.

Supported Channels

We support 22 channels from the french TV broadcast (TNT), with the supported features below.

Channel name Channel Id Supported metadata
TF11FULL SUPPORT
France 22FULL SUPPORT
France 33FULL SUPPORT
Canal +4FULL SUPPORT (non-crypted programs only)
France 55FULL SUPPORT
M66FULL SUPPORT
Arte7FULL SUPPORT
D88FULL SUPPORT
W99FULL SUPPORT
TMC10FULL SUPPORT
NT111FULL SUPPORT
NRJ1212FULL SUPPORT
LCP13FULL SUPPORT
France 414FULL SUPPORT
BFM TV15Snapshots only
iTélé16Snapshots only
D1717FULL SUPPORT
France Ô19FULL SUPPORT
Gulli18FULL SUPPORT
HD120FULL SUPPORT
6ter22FULL SUPPORT
RMC Découverte24FULL SUPPORT

Since parameter behaviour

Most of the endpoints accept a “since” parameter which is the minimum timestamp requested for the returned tags.

It is strongly recommended to use efficiently this parameter when polling the API.

For bandwith-optimization reasons, in case this parameter is not provided or is set to 0, then an automatic since is applied, valued with the timestamp of the latest tag retrieved by the same API user. As a consequence, if you request a given resource without a since value twice, the second request won't return any tags (unless a new tag appeared between the 2 requests of course.)