|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
RGS Decision API (ranked 3428 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/KU4eHm7am6Y0n4r1eJ8Bv_rgs_decision_api_json.jsonGENERAL INFORMATION
Dun & Bradstreet Nordic Risk Decisioning
The Dun & Bradstreet Nordic Risk Decisioning Service API takes an identification number called nationalId and a country code identifying the source country for the subject, both which are used for fetching valid data about the given subject. In addition, a rulesetKey is used for selecting the correct type of process in the rule engine with the proper limits and outcomes setup for your particular integration.
<BR><BR>
The output from the decision service contains information about the given subject, enabling you to verify that the correct subject was used. It contains information about the rules that ran during the decision process, what data was used, and what outcomes were the result. An overall decision outcome is based on all the executed rules.
Contact
- Name: D&B
- Name: dnbeu-decisioning-rgs@dnb.com
- Contact API maintainers
License
- Name: Proprietary
- See License
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: A05:2021
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 637 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.2 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!