|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Risk Assessment (ranked 2223 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/W86Hf3airXV2edLSYhi5U_risk_assessment_json.jsonGENERAL INFORMATION
Table of contents
- [API Description] (#api-description)
- [Errors] (#errors)
- [Changelog] (#changelog)
API Description
The purpose of the Risk Assessment API is to be able to assess potential credit risks for Totalkredit and to use the assessment in the mortgage lending process. Risk elements in the assessment can be related to the real property, the borrowers, the encumbrances and/or the easements. An increased credit risk can influence the calculation of FIsecurities, TK Credit Score and TK process for Agreement Finalisation. Risk reasons are predefined reasons that can be applied when assessing the risk for borrowers, encumbrances and easements. Some risk reasons will have a direct impact on the risk assessment (always risk) others need an individual decision (individual assessment) from the advisor.
| Risk Reason IDs (for risk-assessment V2) |
|---|
| loan-forbearance |
| economic-recovery |
...
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 157 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 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!