Rone Arena API
v1.2.3

User Endpoints

Authentication and player profile APIs.

Requests go to https://arena.rone.dev/api. Forms are generated from the OpenAPI schema.

Jump to endpoint

POST /api/user/auth/send-vc

Send Verification Code

Open on its own page

Send an in-game verification code to the player's account, valid for 5 mins. This endpoint is part of the authentication flow and is used to validate ownership of a game account.

Request body:

  • role_id: Player role identifier (Game ID).
  • zone_id: Server zone identifier (Server ID).

The response confirms whether the verification code was successfully dispatched:

  • code: Status code (0 indicates success).
  • data: Empty string (no payload returned).
  • msg: Message string (e.g., 'ok').

Useful for account authentication flows, linking user identity, and validating account ownership.

Example response 
{
  "code": 0,
  "data": "",
  "msg": "ok"
}
application/json
POST /api/user/auth/send-vc

POST /api/user/auth/login

Login with Verification Code

Open on its own page

Authenticate the player using a verification code to obtain a JWT and session token. This endpoint completes the account login flow, establishes a secure session, and enables authorized access to user-specific resources.

Request body:

  • role_id: Player role identifier.
  • zone_id: Server zone identifier.
  • vc: Verification code sent to the player via in-game mail, valid 5 mins.

The response includes authentication details:

  • code: Status code (0 indicates success).
  • data.jwt: JSON Web Token used for subsequent authenticated requests.
  • data.token: Session token string.
  • data.roleid: Player role ID.
  • data.zoneid: Player zone ID.
  • data.time: Timestamp of login.
  • data.module, name, email, mobile, open_id: Metadata fields (may be empty depending on account).

The response confirms successful login and provides the credentials required for accessing other user endpoints.

Example response 
{
  "code": 0,
  "data": {
    "email": "",
    "jwt": "eyJhbGciOiJI...REDACTED",
    "mobile": "",
    "module": "",
    "name": "",
    "open_id": "",
    "roleid": 1234567890,
    "time": 1774975992,
    "token": "MTc3ND...REDACTED",
    "zoneid": 1234
  },
  "msg": "ok"
}
application/json
POST /api/user/auth/login

POST /api/user/auth/logout

Logout JWT

Open on its own page

Invalidate the player's session using the JWT obtained from /api/user/auth/login. This endpoint terminates the current authenticated session, ensuring that the JWT can no longer be used for authorized requests.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

The response confirms whether the logout was successful:

  • code: Status code (0 indicates success).
  • data: Empty string (no payload returned).
  • msg: Message string (e.g., 'ok').

Note: Although the login response also includes a token field, only the JWT is required for logout. The server uses the JWT to invalidate the session.

Example response 
{
  "code": 0,
  "data": "",
  "msg": "ok"
}
POST /api/user/auth/logout

GET /api/user/info

User Info JWT

Open on its own page

Retrieve the authenticated player's base profile information using a valid JWT. Supports query parameter for localization (lang). Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • lang: Language code for localized content (default: en).

The response includes player details:

  • avatar: Avatar image URL.
  • name: Display name.
  • level: Current player level.
  • rank_level: Current rank level.
  • history_rank_level: Highest historical rank level.
  • reg_country: Registered country code.
  • roleId: Player role identifier.
  • zoneId: Server zone identifier.

Useful for displaying identity card information, verifying account ownership, and populating player profile data in client applications.

Example response 
{
  "code": 0,
  "data": {
    "avatar": "https://wsrv.nl/?url=https%3A%2F%2Fakmpicture.youngjoygame.com%2Fdist%2Fface%2F57060%2F66%2F96%2F1149309666_26_new_9ced56d6-3625-48c3-85d1-0b862a2044e7.jpg",
    "history_rank_level": 9999,
    "level": 200,
    "name": "SAYA AKAN LAWAN",
    "rank_level": 8000,
    "reg_country": "ID",
    "roleId": 1234567890,
    "zoneId": 123456
  },
  "msg": "ok"
}
lang · query

Language code for localized content.

GET /api/user/info

GET /api/user/stats

User Statistics JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's overall statistics using a valid JWT. Supports query parameter for localization (lang). Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • lang: Language code for localized content (default: en).

The response includes general player statistics:

  • wc: Win Count (total matches won).
  • tc: Total Count (total matches played).
  • as: Average Score (overall performance rating, as/100).
  • gt: Game Time (total play time duration in hours).
  • mvpc: MVP Count (number of times player earned MVP).
  • wsc: Win Streak Count (longest consecutive wins).

Hero-specific highlights:

  • mo: Most Often (hero most damage dealt).
  • hk: Highest Kills (hero with the most kills).
  • ma: Most Assists (hero contributing the most assists).
  • ms: Most Score (hero with the highest accumulated score).
  • mdt: Most Damage Taken (hero absorbing the most damage).
  • mg: Most Gold (hero earning the most gold).
  • mtd: Most Total Damage (hero dealing the most damage overall).

Each hero highlight includes metadata such as:

      • v: Value or statistic for the highlight. if ms is used, it calculates v/100.
      • ts: Timestamp of the highlight.
      • hid: Hero ID.
      • n: Hero name.
      • ix: Hero image URL.
      • i2x: Large hero image URL.
      • bid: Battle ID reference.

This endpoint is useful for:

  • Analyzing overall player performance.
  • Identifying favorite heroes.
  • Showcasing personal achievements in Mobile Legends: Bang Bang.
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "b506b47e790797eb1f9762d2f1586496",
  "data": {
    "wc": 188,
    "tc": 308,
    "as": 762.3552,
    "gt": 77.95,
    "mvpc": 73,
    "wsc": 11,
    "mo": {
      "v": 112848,
      "ts": 1726010389,
      "hid": 36,
      "bid": 4110381620662451700,
      "sid": 0,
      "hid_e": {
        "id": 36,
        "n": "Aurora",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fgms%2Fimage%2Fed2295c60bd772b89b7bdbbc2aee6095.png",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_58b97db6a5c286059057d42289612b16.jpg"
      },
      "bid_s": "4110381620662451526"
    },
    "hk": {
      "v": 25,
      "ts": 1672500616,
      "hid": 84,
      "bid": 4108435467847910000,
      "sid": 0,
      "hid_e": {
        "id": 84,
        "n": "Ling",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_af4312bae7aa443129b46a17b4dce3a6.png",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_f76a7dfe805afa316e5ec44295b75772.jpg"
      },
      "bid_s": "4108435467847910024"
    },
    "ma": {
      "v": 31,
      "ts": 1725653347,
      "hid": 20,
      "bid": 4109721990994840000,
      "sid": 0,
      "hid_e": {
        "id": 20,
        "n": "Lolita",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fgms%2Fimage%2Fce1c7af1a946f70585e40296ba85c9c0.jpg",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_1bc4973e512cf4958fe639e12391666e.jpg"
      },
      "bid_s": "4109721990994840266"
    },
    "ms": {
      "v": 1330,
      "ts": 1715555863,
      "hid": 84,
      "bid": 4110821683001146000,
      "sid": 0,
      "hid_e": {
        "id": 84,
        "n": "Ling",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_af4312bae7aa443129b46a17b4dce3a6.png",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_f76a7dfe805afa316e5ec44295b75772.jpg"
      },
      "bid_s": "4110821683001146109"
    },
    "mdt": {
      "v": 372063,
      "ts": 1727227888,
      "hid": 20,
      "bid": 4109978035471765500,
      "sid": 0,
      "hid_e": {
        "id": 20,
        "n": "Lolita",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fgms%2Fimage%2Fce1c7af1a946f70585e40296ba85c9c0.jpg",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_1bc4973e512cf4958fe639e12391666e.jpg"
      },
      "bid_s": "4109978035471765660"
    },
    "mg": {
      "v": 22282,
      "ts": 1718939040,
      "hid": 84,
      "bid": 4116060748536699000,
      "sid": 0,
      "hid_e": {
        "id": 84,
        "n": "Ling",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_af4312bae7aa443129b46a17b4dce3a6.png",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_f76a7dfe805afa316e5ec44295b75772.jpg"
      },
      "bid_s": "4116060748536698631"
    },
    "mtd": {
      "v": 27152,
      "ts": 1719290587,
      "hid": 65,
      "bid": 4110233968270030300,
      "sid": 0,
      "hid_e": {
        "id": 65,
        "n": "Claude",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_7ed528f154dd4f460c59361ab0ed7942.png",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_1edf19b0839ffd2bffb60b4ee4953239.jpg"
      },
      "bid_s": "4110233968270030438"
    },
    "sids": [
      40,
      39,
      38,
      37
    ]
  }
}
lang · query

Language code for localized content.

GET /api/user/stats

GET /api/user/privacy/settings

User Privacy Settings JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's privacy settings using a valid JWT. Supports query parameter for localization (lang). Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • lang: Language code for localized content (default: en).

The response includes:

  • popup_shown: Whether the privacy popup has been shown to the user.
  • privacy: Current privacy state (true/false).
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "410b98229c4a2ab35edddb49df774922",
  "data": {
    "popup_shown": true,
    "privacy": false
  }
}
lang · query

Language code for localized content.

GET /api/user/privacy/settings

POST /api/user/privacy/settings

Update User Privacy Settings JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Update the authenticated player's privacy settings using a valid JWT. Supports query parameter for localization (lang). Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • visibility: Visibility mode. Use visible to allow friends to view your profile, and invisible to hide your profile from friends. This parameter is required.
  • lang: Language code for localized content (default: en).
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "410b98229c4a2ab35edddb49df774922",
  "data": {
    "popup_shown": true,
    "privacy": false
  }
}
visibility · query

Profile visibility mode. Choose visible to let friends view your profile, or invisible to hide your profile from friends.

lang · query

Language code for localized content.

POST /api/user/privacy/settings

GET /api/user/season

User Season List JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's season information using a valid JWT. Supports query parameter for localization (lang). Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • lang: Language code for localized content (default: en).

The response includes:

  • sids: List of season identifiers representing the seasons in which the player has participated or has tracked statistics.

This endpoint is useful for:

  • Displaying season history.
  • Linking performance data to specific seasons.
  • Enabling clients to fetch season-specific stats or achievements.
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "74879d32961c1784a762671398979ac6",
  "data": {
    "sids": [
      40,
      39,
      38,
      37
    ]
  }
}
lang · query

Language code for localized content.

GET /api/user/season

GET /api/user/matches

User Matches JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's recent matches information using a valid JWT. Supports query parameters for season filtering, pagination, and localization. Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • sid: Season ID for filtering matches (must be a valid season ID from /api/user/season).
  • limit: Maximum number of matches to retrieve (minimum: 1).
  • last_cursor: Cursor for pagination. Use the value from pageInfo.nextCursor in the current response. If pageInfo.hasNext is false or pageInfo.nextCursor is empty, there is no next page.
  • lang: Language code for localized content (default: en).

The response includes match details:

  • sid: Season ID.
  • bid: Battle ID (unique match reference).
  • hid: Hero ID used in the match.
  • k: Kills.
  • d: Deaths.
  • a: Assists.
  • lid: Lane ID (1 EXP, 2 Mid, 3 Roam, 4 Jungle, 5 Gold).
  • s: Score (performance rating for the match, s/100).
  • mvp: MVP flag (1 if MVP, 0 otherwise).
  • res: Result (1 = Win, 0 = Loss).
  • ts: Timestamp of the match.
  • hid_e: Hero entity metadata (hero ID, name, images).
  • bid_s: String battle ID representation.

Pagination example:

First request: /api/user/matches?sid=40&limit=10&lang=en → response includes pageInfo.nextCursor = 4139649383291049463.

Second request: /api/user/matches?sid=40&limit=10&last_cursor=4139649383291049463&lang=en → retrieves the next page, using pageInfo.nextCursor from the current response.

Stop pagination when pageInfo.hasNext = false or pageInfo.nextCursor is empty.

The response also includes pagination metadata:

  • pageInfo.nextCursor: Cursor value for the next page.
  • pageInfo.hasNext: Boolean flag indicating if more results are available.
  • pageInfo.count: Number of results returned in the current page.

This endpoint is useful for:

  • Reconstructing match history.
  • Analyzing player performance.
  • Enabling clients to paginate reliably through a player's matches.
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "53cd62802d24dc512ffd908e1d6d06bc",
  "data": {
    "pageInfo": {
      "nextCursor": "4143043017340290910",
      "hasNext": true,
      "count": 1
    },
    "result": [
      {
        "sid": 40,
        "bid": 4132717739868068400,
        "hid": 17,
        "k": 14,
        "d": 1,
        "a": 11,
        "lid": 4,
        "s": 1180,
        "mvp": 0,
        "res": 1,
        "ts": 1774857999,
        "hid_e": {
          "id": 17,
          "n": "Fanny",
          "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_ae8ca46da01da69619a6c03dc7069921.png",
          "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_74fabc6c0d5db065fbb836b6879f36ca.jpg"
        },
        "bid_s": "4132717739868068534"
      }
    ]
  }
}
sid · query

The season ID for filtering recent matches.

limit · query

The maximum number of recent matches to retrieve. Minimum: 1.

last_cursor · query

Pagination cursor from pageInfo.nextCursor of the current response.

lang · query

Language code for localized content.

GET /api/user/matches

GET /api/user/matches/{match_id}

User Match Details JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's detailed match information using a valid JWT. Supports query parameters for season filtering and localization. Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Path parameters:

  • match_id: Unique identifier of the match (from bid_s in /api/user/matches).

Query parameters:

  • sid: Season ID for filtering (must be a valid season ID from /api/user/season).
  • lang: Language code for localized content (default: en).

The response includes per-player match details:

  • f: Team flag (1 = Team A, 2 = Team B).
  • hid: Hero ID used in the match.
  • rid: Role ID (unique player identifier).
  • zid: Zone ID (server region).
  • k: Kills.
  • d: Deaths.
  • a: Assists.
  • tfr: Team Fight Rate (contribution ratio in team fights, tfr*100%).
  • o: Output (total damage dealt or hero damage).
  • op: Output Percentage (damage contribution relative to team).
  • s: Score (performance rating, s/100).
  • mvp: MVP flag (1 if MVP, 0 otherwise).
  • its: Item IDs equipped during the match.
  • its_e: Item entity metadata:
      • id: Item ID.
      • n: Item name.
      • ix: Item image URL.
      • i2x: Large item image URL.
  • eq: Equipment slot indicator.
  • ts: Timestamp of the match.
  • bd: Battle duration (seconds).
  • fk: First Kill flag (total kills in a team).
  • fw: First Win flag (1 for Win, 0 for Loss).
  • hid_e: Hero entity metadata:
      • id: Hero ID.
      • n: Hero name.
      • ix: Hero image URL.
      • i2x: Large hero image URL.
  • hlvl: Hero level reached in the match.
  • rname: Role name (localized string, e.g., 'ジャングラー').

This endpoint provides a full breakdown of each participant in the match, including:

      • Hero choice.
      • Performance stats (kills, deaths, assists, damage).
      • Items built with metadata.
      • Role assignment and team contribution.

It is useful for:

      • Reconstructing match history.
      • Analyzing team compositions.
      • Evaluating player performance in detail.
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "4d96357b092ade76774481366567bcaf",
  "data": {
    "result": [
      {
        "f": 2,
        "hid": 31,
        "rid": 1880233572,
        "zid": 57027,
        "k": 4,
        "d": 9,
        "a": 6,
        "tfr": 0.4167,
        "o": 83974,
        "op": 0.2202,
        "s": 509,
        "mvp": 0,
        "its": [
          2305,
          3002,
          3005,
          3015,
          3003,
          3013,
          0
        ],
        "eq": 0,
        "ts": 1773837471,
        "bd": 1292,
        "fk": 24,
        "fw": 0,
        "hid_e": {
          "id": 31,
          "n": "Moskov",
          "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fgms%2Fimage%2F5c4587c25e681be1aecfda0cfbe44714.png",
          "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_843f1c2c3a1b2d4da2fc2ec73cf47cfa.jpg"
        },
        "its_e": [
          {
            "id": 2305,
            "n": "Swift Boots",
            "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fhomepage%2F100_b31a355cc85682eed8d9e0dc163fd756.png",
            "i2x": ""
          },
          null
        ],
        "hlvl": 15,
        "rname": "\u1d35\u1d50\u0166ungi\u2113"
      }
    ]
  }
}
match_id · path

The unique identifier of the match to retrieve details for.

sid · query

The season ID for filtering recent matches.

lang · query

Language code for localized content.

GET /api/user/matches/{match_id}

GET /api/user/heroes/frequent

User Frequent Heroes JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's frequent heroes information using a valid JWT. Supports query parameters for season filtering, pagination, and localization. Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • sid: Season ID for filtering frequent heroes (must be a valid season ID from /api/user/season).
  • limit: Maximum number of heroes to retrieve (minimum: 1).
  • last_cursor: Cursor for pagination. Use the value from pageInfo.nextCursor in the current response. If pageInfo.hasNext is false or pageInfo.nextCursor is empty, there is no next page.
  • lang: Language code for localized content (default: en).

The response includes frequent hero usage details:

  • hid: Hero ID.
  • tc: Total Count (number of matches played with this hero).
  • wc: Win Count (number of matches won with this hero).
  • bs: Battle Score (average performance rating, bs/100).
  • mr: Match Rating (accumulated rating points).
  • mrp: Match Rating Percentage (rating contribution relative to overall performance).
  • hid_e: Hero entity metadata:
      • id: Hero ID.
      • n: Hero name.
      • ix: Hero image URL.
      • i2x: Large hero image URL.
  • p: Power score (weighted performance index for ranking frequent heroes, also called MMR).

Pagination example:

First request: /api/user/heroes/frequent?sid=37&limit=5&lang=en → response includes pageInfo.nextCursor = 11.

Second request: /api/user/heroes/frequent?sid=37&limit=5&last_cursor=11&lang=en → retrieves the next page, using pageInfo.nextCursor from the current response.

Stop pagination when pageInfo.hasNext = false or pageInfo.nextCursor is empty.

The response also includes pagination metadata:

  • pageInfo.nextCursor: Cursor value for the next page.
  • pageInfo.hasNext: Boolean flag indicating if more results are available.
  • pageInfo.count: Number of results returned in the current page.

This endpoint is useful for:

  • Analyzing which heroes a player uses most often.
  • Tracking win rates and performance scores.
  • Comparing hero usage across different seasons.
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "6b098c3c683f977217a91bb6c630e7be",
  "data": {
    "pageInfo": {
      "nextCursor": "",
      "hasNext": true,
      "count": 0
    },
    "result": [
      {
        "hid": 17,
        "tc": 8,
        "wc": 7,
        "bs": 844.875,
        "mr": 6626,
        "mrp": 0.6188,
        "hid_e": {
          "id": 17,
          "n": "Fanny",
          "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_ae8ca46da01da69619a6c03dc7069921.png",
          "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_74fabc6c0d5db065fbb836b6879f36ca.jpg"
        },
        "p": 1460
      }
    ]
  }
}
sid · query

The season ID for filtering frequent heroes.

limit · query

The maximum number of frequent heroes to retrieve. Minimum: 1.

last_cursor · query

Pagination cursor from pageInfo.nextCursor of the current response.

lang · query

Language code for localized content.

GET /api/user/heroes/frequent

GET /api/user/matches/hero/{hero_identifier}

User Matches by Hero JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's recent matches filtered by a specific hero using a valid JWT. Supports query parameters for season filtering, pagination, and localization. Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Path parameters:

  • hero_identifier: Hero identifier as numeric hero ID or hero name. Accepts values like 30, Yi Sun-shin, or yisunshin.

Query parameters:

  • sid: Season ID for filtering matches (must be a valid season ID from /api/user/season).
  • limit: Maximum number of matches to retrieve (minimum: 1).
  • last_cursor: Cursor for pagination. Use the value from pageInfo.nextCursor in the current response. If pageInfo.hasNext is false or pageInfo.nextCursor is empty, there is no next page.
  • lang: Language code for localized content (default: en).

Response structure:

  • code: Status code (0 indicates success).
  • message: Response message from upstream service.
  • traceID: Upstream trace identifier for request debugging/tracking.
  • data: Main payload object.
      • pageInfo: Pagination metadata object.
          • nextCursor: Cursor value for the next page, used for pagination.
          • hasNext: Boolean flag indicating whether more results are available.
          • count: Number of results returned in the current page.
      • hi: Aggregated hero summary for the selected hero and season.
          • hid: Hero ID.
          • tc: Total Count (matches played with this hero).
          • wc: Win Count (matches won with this hero).
          • bs: Battle Score (average score; interpret as bs/100 when non-zero).
          • mr: Match Rating points for this hero.
          • mrp: Match Rating percentage/contribution.
          • hid_e: Hero metadata object.
              • id: Hero ID metadata.
              • n: Hero name.
              • ix: Hero image URL.
              • i2x: Large hero image URL.
          • p: Hero power/MMR-style value.
      • result: Array of match entries for this hero.
          • sid: Season ID.
          • bid: Battle ID (numeric).
          • hid: Hero ID used in that match.
          • k: Kills.
          • d: Deaths.
          • a: Assists.
          • lid: Lane ID (1 EXP, 2 Mid, 3 Roam, 4 Jungle, 5 Gold).
          • s: Match score/performance value (commonly interpreted as s/100).
          • mvp: MVP flag (1 if MVP, 0 otherwise).
          • res: Result (1 = Win, 0 = Loss).
          • ts: Match timestamp (unix time).
          • hid_e: Hero metadata object.
              • id: Hero ID metadata.
              • n: Hero name.
              • ix: Hero image URL.
              • i2x: Large hero image URL.
          • bid_s: String battle ID.

Pagination example:

First request: /api/user/matches/hero/17?sid=40&limit=10&lang=en

Next request: /api/user/matches/hero/17?sid=40&limit=10&last_cursor=<pageInfo.nextCursor>&lang=en

Stop pagination when pageInfo.hasNext = false or pageInfo.nextCursor is empty.

Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "15b79802139dd7766774f6e84ffc31bd",
  "data": {
    "pageInfo": {
      "nextCursor": "",
      "hasNext": false,
      "count": 0
    },
    "hi": {
      "hid": 17,
      "tc": 9,
      "wc": 8,
      "bs": 0,
      "mr": 6788,
      "mrp": 0.6641,
      "hid_e": {
        "id": 17,
        "n": "Fanny",
        "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_ae8ca46da01da69619a6c03dc7069921.png",
        "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_74fabc6c0d5db065fbb836b6879f36ca.jpg"
      },
      "p": 1496
    },
    "result": [
      {
        "sid": 40,
        "bid": 4138442308503475824,
        "hid": 17,
        "k": 7,
        "d": 3,
        "a": 7,
        "lid": 4,
        "s": 810,
        "mvp": 0,
        "res": 1,
        "ts": 1774955310,
        "hid_e": {
          "id": 17,
          "n": "Fanny",
          "ix": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Fimg%2Fmlbb%2Fcommunity%2F100_ae8ca46da01da69619a6c03dc7069921.png",
          "i2x": "https://wsrv.nl/?url=https%3A%2F%2Fakmweb.youngjoygame.com%2Fweb%2Fsvnres%2Ffile%2Fmlbb%2Fhomepage%2F100_74fabc6c0d5db065fbb836b6879f36ca.jpg"
        },
        "bid_s": "4138442308503475824"
      }
    ]
  }
}
hero_identifier · path

Hero identifier as numeric hero ID or hero name. Accepts values like 30, Yi Sun-shin, or yisunshin. Name matching ignores spaces/symbols and is case-insensitive (e.g., Luo Yi to luoyi).

sid · query

The season ID for filtering matches by hero.

limit · query

The maximum number of matches to retrieve. Minimum: 1.

last_cursor · query

Pagination cursor from pageInfo.nextCursor of the current response.

lang · query

Language code for localized content.

GET /api/user/matches/hero/{hero_identifier}

GET /api/user/friends

User Friends JWT Deprecated

Open on its own page

Deprecated. It may change or disappear in a future version, so avoid it in new integrations.

Retrieve the authenticated player's friends information using a valid JWT. Supports query parameters for season filtering and localization. Requires an Authorization header with the JWT from login.

Headers:

  • Authorization: Bearer <jwt> (JWT obtained during login).

Query parameters:

  • sid: Season ID for filtering friends (must be a valid season ID from /api/user/season).
  • lang: Language code for localized content (default: en).

The response includes friend statistics and metadata:

  • bfs: Best Friends (highlighted or prioritized friends list, may be null).
  • wfs: Weekly Friends (friends interacted with recently, may be empty).
  • fs: Friends list entries, each containing:
      • f: Friend object with identifiers:
          • rid: Role ID (unique player identifier).
          • zid: Zone ID (server region).
          • n: Name (may be empty if private).
          • ax: Avatar URL (may be empty).
          • pri: Privacy flag (true if details are hidden).
      • frid: Friend Role ID (unique identifier for the friend).
      • fzid: Friend Zone ID (server region for the friend).
      • cl: Current Level of the friend.
      • l: Level (same as cl, sometimes duplicated).
      • tbc: Total Battle Count (matches played together).
      • twc: Total Win Count (matches won together).

This endpoint is useful for:

  • Displaying a player's friend list.
  • Tracking shared match history.
  • Analyzing cooperative performance with friends across different seasons.
Example response 
{
  "code": 0,
  "message": "Success",
  "traceID": "e0516a11c845c6ca93a1a43178c2f510",
  "data": {
    "wfs": [],
    "fs": [
      {
        "f": {
          "rid": 0,
          "zid": 0,
          "n": "",
          "ax": "",
          "pri": true
        },
        "frid": 0,
        "fzid": 0,
        "cl": 42,
        "l": 42,
        "tbc": 7,
        "twc": 6
      }
    ]
  }
}
sid · query

The season ID for filtering friends.

lang · query

Language code for localized content.

GET /api/user/friends