|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Jenz API (ranked 2277 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/IPnxtRghJtUMpKH_ykFCP_jenz_api_json.jsonGENERAL INFORMATION
Jenz is an internal communication tool that strengthens company culture and builds a transparent workplace. This is our Public API that enables you to create your own custom integrations around Jenz
Please read these basic instructions before you start working with the API. As the first step, you need to send a username and password to the /api/token
endpoint in order to receive the JWT token. JWT then needs to be send on every subsequent request in the form of HTTP header Authorization: Bearer {JWT}
.
Allowed HTTPs requests include:
- POST - to create a resource
- PATCH - to update a resource
- GET - to get a resource or a list of resources
- DELETE - to delete a resource
Here is the description of common server responses:
- 200
OK
- the request was successful (some API calls may return 201 instead). - 201
Created
- the request was successful and a resource was created. - 204
No Content
- the request was successful but there is no representation to return (i
...
Contact
- Name: API Support
- Name: it@jenz.app
- Contact API maintainers
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 122 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 2.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!