Glossary[Glossary GET](/docs/glossary/get-glossary.md)

# Glossary

Server URL`loading...`

GET

/`glossary`

Send

Query

category`string`Unset

Every World of Tanks term the site defines: game mechanics, vehicle statistics, battle formats, rating systems and community slang. Each entry carries a one-sentence definition, the other spellings it is searched by, and the section it belongs to. Alphabetical by term. Pass `category` to read one section.

## [Query Parameters](#parameters-query)

category?string

Section of the glossary a term belongs to.

Value in

-   "vehicles"
-   "gunnery"
-   "armor"
-   "mobility"
-   "vision"
-   "crew"
-   "progression"
-   "economy"
-   "ratings"
-   "statistics"
-   "modes"
-   "tactics"
-   "slang"

## [Response Body](#response-body)

### 200

`application/json`

cURL

JavaScript

Go

Python

Java

C#

Rust

```
curl -X GET "https://example.com/glossary"
```

200

```
{  "results": [    {      "slug": "string",      "term": "string",      "aliases": [        "string"      ],      "category": "vehicles",      "short": "string"    }  ]}
```

[

Map videos GET

Every published battle the community has linked on this map, newest approved first, whatever format it was played in and whatever it was played in. This is the read behind a tactic library: a Clan Wars or Advances battle is filed under the ground it was fought on and the side it was fought from, not under a vehicle, so the map is the only page it can be looked up from. Random battles come back alongside them, carrying the tank they were played in, and the page filters by format.

](/docs/maps/get-region-maps-slug-videos.md)[

Glossary anchors GET

Where each glossary term attaches to the interface: the tank specification columns and the on-screen labels it defines, with the one-sentence definition to show for them. Small by construction (only anchored terms, listed once each), so a client can hold the whole thing and explain a table without another request.

](/docs/glossary/get-glossary-anchors.md)

## Navigation

- [unicum.gg](/index.md)

## Indexes

- [llms.txt](/llms.txt): the API, the MCP server and the other machine-readable surfaces.
- [llms-full.txt](/llms-full.txt): the same, with every endpoint's parameters inline.
- [sitemap.md](/sitemap.md): every section of the site, down to the individual pages.