The state of public APIs| Submit an API

|API RANK| by Escape.tech

Benchmark and ranking of 5138+ public APIs by Escape.tech

Back to the list Request ranking update

KickEx API Beta (ranked 4813 of 5138)

https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/m2mw76ecJl92dEKI_cxnf_kickex_api_beta_json.json

GENERAL INFORMATION

Authentication

For client authentication and integrity control the following attributes should be added to the request headers

KICK-API-KEY - First you should create a new API key, and then use the key value as KICK-API_KEY in all requests that require authentication.
KICK-API-PASS - API key passphrase. Should be encoded (base64_encode) before adding it to the request header). Passphrase requirements:
- length between 20 and 160 characters
- contains lower-case English letters
- contains upper-case English letters
- contains numbers
KICK-API-TIMESTAMP - TIMESTAMP of the request (unix timestamp, seconds)
KICK-SIGNATURE - request signature. Request signature is need for the integrity control of the request on server-side. To create the request signature you need to use API Secret that is not included in the request headers.
```
function base64url_decode($data) {
  return base64_decode(str_replace(array('-', '_'), array('+', '/'), $data));
```

...

Contact

Name: support@kickex.com

License

Name: Apache 2.0
See License

SECURITY 4/5

The security score of an API is computed as the number of OWASP top 10 vulnerabilities detected in the API.

OWASP issues detected: API7:2023

PERFORMANCE 4/5

The performance score is derived from the median response time of the API, sometimes referred as p50. The median is the value separating the higher half from the lower half of a data sample, here the response times of the API.

The median response time of the API is 176 ms .

Get p50 under 220 ms to get a 4/5 score.

RELIABILITY 0/5

The reliability score is derived from the number of inconsistent server responses, either server errors or non-conforming return values.

Self compliance: response objects matched the declared response types.
Server errors: the server returned 5xx errors.

DESIGN 3/5

The design score reflects the quality of the specification file (usually named openapi.json or swagger.json). Having a high-quality specification file (with up-to-date types and examples) help developers understand the API and tools produce relevant documentation.

Respects OpenAPI 3.0.0 schema specification.
Contains comments and summaries.
Contains examples.
Does not contain duplicated objects.

Popularity 0/5

The popularity score is computed from the number of references to the API found on the internet. Have your API used by many developers to get a higher score!