|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
ClickSend REST API v3 (ranked 3047 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/ClickSend_REST_API_v3_7fe73427_7a3f_41bf_b0a7_ddf95efb8fa6_yaml.yamlGENERAL INFORMATION
This is the official API documentation for ClickSend.com
Below you will find a current list of the available methods for clicksend.
NOTE: You will need to create a free account to use the API.
You can
Register Here.
API URL
The API should always be accessed over SSL.
Base URL: https://rest.clicksend.com/v3/
Authentication
Basic HTTP authentication should be used in the header.
Either:
username
: Your API username
password
: Your API key
You can get your API credentials by clicking 'API Credentials' on the top right of the dashboard.
OR
username
: Your account username
password
: Your account password
These are the same credentials that you use to login to the dashboard.
Authorization Header
The Authorization header is constructed as follows:
- Username and password are combined into a string
username:password
- The resulting string is then encoded using Base64 encoding
...
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 1/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 1,120 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 5/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 did not return any 5xx error.
DESIGN 4/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!