|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Ino-Vibe API (ranked 4001 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/K3NddI7bIv2sXbFoABRTF_ino_vibe_api_json.jsonGENERAL INFORMATION
본 문서는 Ino-Vibe API 사용법에 대한 안내를 제공합니다.
API를 통해서 사용 그룹에게 등록된 디바이스의 정보와 파형 데이터를 확인할 수 있습니다.
모든 API는 JWT 인증을 요구합니다. 그리고 JWT를 발급 받기 위해서는 API를 호출하기 전에 /oauth/token API를 통해서 토큰을 발급 받아야 합니다.
토큰을 받기 위해서는 사용자 그룹의 클라이언트 정보가 필요합니다. 이 클라이언트 정보는 이노온에서 등록해주어야 하며,
새로 발급 받아야 하는 경우 이노온에 문의 바랍니다.
Contact
- Name: contact
- Name: contact@ino-on.com
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,040 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 2/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!