|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Leegality Documentation Gateway (ranked 843 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/5nu3tKrrC45zsTg8JkWK__leegality_documentation_gateway_json.jsonGENERAL INFORMATION
Welcome to the reference for the Leegality REST API!
You can use our API for creating, editing and deleting Signing invitations; for fetching Documents, Audit Trails and other details for existing invitations; and for searching documents based on your custom query.
The API is based on REST principles, and is a JSON-backed interface.
Integration Flow
In terms of the flow-
-
The first step is to create a Sign Invitation by making a POST call to the Create API from your back-end server.
a. One Sign Invitation can be used to get a single PDF file eSigned.
b. You can add any number of signers to an invitation. A signer is called an invitee. By default, a signer order is assigned to the request as per which the invitations of subsequent invitees are only activated on successful eSigning by the previous invitees. You can also deactivate Signing order if your use case so requires.
c. You need to mandatorily pass the Name, email and/or phone number of the invitee to
...
Contact
- Name: Leegality Support
- Name: support@leegality.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 127 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 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!