Endpoint
List codenames
GET /api/{game}/codenames.json
Riot ships one set of names to players and another everywhere else. This indexes them in the direction you arrive from: internal name first.
Path parameters
| game | string | A game slug from the index. |
Response
The reverse index for one game.
| codenames | Codename[] | One entry per named thing. |
| codenames[].codename | string | Riot’s internal name, as it appears in asset paths and actor classes. |
| codenames[].kind | string | agent, map or weapon. |
| codenames[].name | string | What players call it. |
| codenames[].slug | string | The agent slug, or the entity id for a map or weapon. |
| codenames[].entities | string[] | Entity ids carrying this codename. |
The build refuses to emit an index where two things claim one codename: an ambiguous reverse lookup is worse than none.
Request
curl -s -H "x-api-key: $KB_API_KEY" https://kb.play-ascend.com/api/valorant/codenames.json
Response example
{
"schemaVersion": 3,
"profile": {
"developer": "Riot Games",
"publisher": "Riot Games",
"released": 2020,
"genre": "tactical hero shooter",
"modes": [
"Unrated",
"Competitive",
"… 5 more"
]
},
"attribution": "Ability figures are facts extracted from Riot Games' official VALORA…",
"codenames": [
{
"codename": "AK",
"kind": "weapon",
"name": "Vandal",
"slug": "vandal",
"entities": [
"vandal"
]
},
{
"codename": "Aggrobot",
"kind": "agent",
"name": "Gekko",
"slug": "gekko",
"entities": [
"gekko-dizzy",
"gekko-mosh-pit",
"… 2 more"
]
},
"… 65 more"
]
}