|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Self Sovereign Identity (ranked 129 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/kWI8Omx3vcKa68nI8qpfa_self_sovereign_identity_json.jsonGENERAL INFORMATION
Self Sovereign Identity (SSI) APIs provide services to create and manage Proof Requests on the SSI domain.
They allow API consumers to create a Proof Request specifying a list of credentials to be included,
and to retrieve the metadata (such as a deeplink or a web url)
which are needed for an end user to send a Proof presentation to a specific SSI agent.
The SSI services own the responsibility for the Proof Request lifecycle and for the event handling, abstracting the underlying SSI protocols and processes.
Upon the creation of a Proof request, a unique correlation ID is generated to identify the credential exchange process
across the consumer and the SSI services. It can be used to retrieve the actual status of an existing Proof Request
and to correlate received Proof Presentation or other events.
The API design is agnostic of the specific SSI protocol used at the implementation layer and the adopted SSI credential schemas.
Contact
- Name: greg.nittner1@vodafone.com
License
- Name: Apache 2.0
- 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: API7:2023
PERFORMANCE 5/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 58 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 3/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 3/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!