|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
StrongAuth 3rd-party App Integration Docs (ranked 366 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/9ySbQGS9pMwT6QI9Kd1MQ_strongauth_3rd_party_app_integration_docs_json.jsonGENERAL INFORMATION
The collection describes all the endpoints useful to create an authorization request in either syncronous or asyncronous manner on StrongAuth Service. The apis require a specific user to be registered on StrongAuth. The user gets notified via a push notification and is requested of either approval or rejection of the request via StrongAuth Mobile Application. The AuthRequest apis need of </br></br> 1. <b>userId</b>, referring to outstanding id on Intesa San Paolo LDAP service</br> 2. <b>message</b>, to be displayed on notification</br> 3. <b>apiKey</b>, specific to the 3rd party application to invoke StrongAuth Service</br> 4. <b>callbackUrl</b>, (for asynchronous request only) referring to the invoked endpoint at the end of authorization process
Contact
- Name: davide.parlapiano@pwc.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 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 120 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 2/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!