A. Newly developed game
1. New Game Integration Implementation (Example: Miracle Slide)
1.1 [Join API] - API for Account Verification during Match Participation (Current Minimum Requirements)
| Category | Details | Purpose | Type | Composition |
|---|---|---|---|---|
UUID | Unique ID of the user | MiraclePlay matching check | POST | Mandatory |
NickName | For the existence check, use a True/False call | Verify if the user exists in the game | POST | Mandatory |
ClientVer | Client version information | Ensure minimum game version compatibility for participants | POST | Optional |
AccessKey | Access key for data security | Additional mandatory input fields when calling the API (the approach may vary by developer) | POST | Optional |
API URL |
|
|
|
|
1.2 [GameData API] API for Recording Match Results (Varies for Each Game)
| Category | Details | Purpose | Type | Composition |
|---|---|---|---|---|
UUID | Unique ID of the user | MiraclePlay matching check | POST | Mandatory |
NickName | - | Use the MiraclePlay nickname | POST | Optional |
ClientVer | Client version information | Participant's version check during play | POST | Optional |
Starttime | Game start time (GMT) | Aggregation of match results | POST | Game-specific |
Endtime | Game endAggregation of match resultstime (GMT) | Aggregation of match results | POST | Game-specific |
Score | Recorded result data | Aggregation of match results | POST | Game-specific |
playTime | Total playtime | Aggregation of match results | POST | Game-specific |
AccessKey | Access key for data security | Additional mandatory input fields when calling the API (the approach may vary by developer) | POST | Optional |
Last updated