|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Lahzenegar API (ranked 3815 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/G_mq_TtY5SaKrhbiwz_mx_lahzenegar_api_json.jsonGENERAL INFORMATION
API ENDPOINTS
All endpoints are only accessible via https and are located here:
https://api.lahzenegar.com/v3
STRUCTURE
THE ENVELOPE
Every response is contained by an envelope. That is, each response has a predictable set of keys with which you can expect to interact:
{
“meta” : {
“code” : 200
},
“data” : {
...
},
“pagination” : {
“next_url” : ...,
“next_max_id” : “1324452”
}
}
META
The meta key is used to communicate extra information about the response to the developer. If all goes well, you'll only ever see a code key with value 200. However, sometimes things go wrong, and in that case you might see a response like:
{
“meta” : {
“code” : 400,
“developer_message” : ...,
“user_message” : ...
}
}
DATA
The data key is the meat of the response. It may be a list or dictionary,
but either way this is where you'll find the data you requested.
PAGINATION
Sometimes you just can't get enough. For th
...
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 2/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 556 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 1/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!