|API RANK| by Escape.tech
Benchmark and ranking of 5138+ public APIs by Escape.tech
[Global] TGG Games API (ranked 2451 of 5138)
https://escape-data-and-specs.s3.fr-par.scw.cloud/specs/knFeOYUjNrO_B8_G5UsLn_global_tgg_games_api_json.jsonGENERAL INFORMATION
Overview
Wallet Interface
Wallet should allow games to handle financial transactions differently
- some support bet reservation, others don’t
- some operate on payment (transaction) level, some on round level
- ….
In order to implement 'generic' support, wallet must be able
- to take appropriate actions if it is notified about round end (for example approve all payments in
that round) - to take appropriate actions if it is notified about transaction change (approval of specific payment). For example if bet is approved wallet can check if this was only payment in round and that also triggers actions needed to be done on wallet when round finishes
Sometimes same request will be issued twice or more times towards platform. Reason for this could be that response was not received from platform for previous request or something else went wrong (network glitch, error in communication with RGS, general error …). So same request can be reissued. Platform must respond in idempotent way
...
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 205 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 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!