---
search:
  tags:
    - Accounts
    - POST
seo:
  description: >-
    Returns the badges of your own account: one entry per app and badge type,…
    Reference for the POST /v1/account.me.listBadges endpoint in the SteamSets
    API.
sidebar:
  label: List your crafted badges
  badge: POST
title: List your crafted badges
type: openapi-operation
---
Returns the badges of your own account: one entry per app and badge type, with the highest level crafted.

`badgeIds` lists the SteamSets id of every crafted level of that badge. An event or sale app can have more than one badge per type.

### Paging

A page holds 5,000 badges by default and up to 20,000. Send `nextCursor` back as `cursor` for the next page. Use `appIds` to ask for some apps only.

### Freshness

The data is as fresh as `badgesUpdatedAt`.

### Cost

This route is free. Your own data uses no units of the key's daily allowance.

### Example

```json
{
  "badges": [
    { "appId": 730, "isFoil": false, "level": 5, "xp": 500, "completedAt": "2025-05-01T12:00:00Z", "badgeIds": ["bdg_1", "bdg_5"] }
  ],
  "badgesUpdatedAt": "2026-11-15T08:30:00Z",
  "nextCursor": null
}
```

`POST /v1/account.me.listBadges`

**Request body** (`application/json`, required)

- `appIds` (integer<int32>[] | null) — Only these apps. Leave it out for every app.
- `cursor` (string) — The nextCursor of the previous page. Leave it out for the first page.
- `limit` (integer<int64>) — Badges per page.

Request body example:

```json
{
  "appIds": [
    730
  ],
  "cursor": "730_normal",
  "limit": 5000
}
```

**Responses**

- `200` — OK
- `400` — Bad Request
- `401` — Unauthorized
- `422` — Unprocessable Entity
- `500` — Internal Server Error

Response example, 200:

```json
{
  "badges": [
    {
      "appId": 0,
      "badgeIds": [
        "bdg_123"
      ],
      "completedAt": "2019-08-24T14:15:22Z",
      "isFoil": true,
      "level": 0,
      "xp": 0
    }
  ],
  "badgesUpdatedAt": "2019-08-24T14:15:22Z",
  "nextCursor": "string"
}
```
