|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
LEM Verify API (ranked 4922 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/eWPxfQ3AJXK3fgPgTkGUt_lem_verify_api_json.jsonGENERAL INFORMATION
Identity Document Verificaiton (IDV) and Anti Money Laundering (AML) API
The LEM Verify API and webhook integration is organised around REST using standard HTTP response codes and verbs. The current version of our API generates unique URLs for verifications, such as Combination, Document and Liveness, along with a notification system in the form of Webhooks. When a verification has been processed by the system, LEM Verify will send a POST request (Webhooks) to the selected webhook URL with the result, details and PDF report for further processing by your system.
Your LEM Verify account ID found in the Account Setup section of the dashboard and the x-lem-key can be enabled from the Connections > Webhook section of your LEM Verify dashboard
Example Use Case - Generate unique URL for Document and Liveness request
Your system needs to verify a person's identity for your KYC/AML process. By making a simple API call to "Request a Combination" (a combination of document and
...
Contact
- Name: support@lemverify.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 3/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 382 ms .
Get p50 under 220 ms to get a 4/5 score.
RELIABILITY 1/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 returned 5xx errors.
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!