|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
Tsunami WebAPI (ranked 2664 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/ABnURXOkr9dkiQSK8_VZL_tsunami_webapi_json.jsonGENERAL INFORMATION
Below are the few parameters description -
<b>CustomerId</b> - Unique Id of Customer/Association/Brewer. Entire system working based on this unique CustomerId. It will be unique for each customer/app and we pass this in each API call. You can find that CustomerId from Admin portal.(i.e for Ohio – 356, NY – 103)
<b>UserUniqueId</b> - This is UserId/ContactId of user who download app. It will be unique for each user. When the user first time register/login via app, the unique ContactId will be generated. You can find this unique contact Id from Admin portal under CRM tab. <b>(NOTE: For old Guild app new ContactId generated for each app if email is same,with new Trail App its only one and only mapping added with that customer)</b>
<b>UniqueId</b> - Randomly Generated unique identifier at the first time when user login / Register in app from device.Use to identify device and user.
<b>RewardId</b> - UniqueId of Product which will be claimed by user.
<b>ProgramId</b> - Loy
...
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 192 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 1/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 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!