---
title: "Updates badge configuration."
method: PATCH
path: "/legacy-badges/v1/badges/{badgeId}"
tags: ["Badges"]
---

# Updates badge configuration.

`PATCH /legacy-badges/v1/badges/{badgeId}`

## Request

- Base URL: `https://apis.roblox.com`
- URL: `https://apis.roblox.com/legacy-badges/v1/badges/{badgeId}`
- Auth: one of:
  - API key in header `x-api-key`
  - OAuth 2
    - Authorization code: `https://apis.roblox.com/oauth/v1/authorize`
    - Token URL: `https://apis.roblox.com/oauth/v1/token` scopes: `legacy-universe.badge:write`, `legacy-universe.badge:manage-and-spend-robux`

Managers may change enabled state, name, and description when authorized for the badge.

## Path parameters

- `badgeId` integer, required

## Request body

- RobloxBadgesApiUpdateBadgeRequest: A request model used for updating badge information.
  - `name` string: The new badge name.
  - `description` string: The new badge description.
  - `enabled` boolean: The new enabled state of the badge.

## Response `200`

OK

- RobloxWebWebAPIApiEmptyResponseModel

## Other responses

- `400`: 6: Text moderated. 14: Invalid badge name. 15: Invalid badge description.
- `401`: 0: Authorization has been denied for this request.
- `403`: 0: Token Validation Failed 2: You do not have permission to manage this badge.
- `404`: 1: Badge is invalid or does not exist. 3: The game is invalid or does not exist.

## Changes

- **2026-10-09** `a088ae4955d2`: 2 info
  - the security scope `legacy-universe.badge:manage-and-spend-robux` was added to the endpoint's security scheme `roblox-oauth2`
  - the security scope `legacy-universe.badge:write` was added to the endpoint's security scheme `roblox-oauth2`

[Operation history](https://skmtc.dev/roblox/apis/roblox-api/changes/legacy-badges/v1/badges/:badgeId/patch.md)

---

[API](https://skmtc.dev/roblox/apis/roblox-api.md) - [All operations](https://skmtc.dev/roblox/apis/roblox-api/llms.txt) - [OpenAPI document](https://skmtc.dev/roblox/apis/roblox-api/revisions/bcfdc20689cd?raw)