---
title: "Issue a league cooldown"
method: POST
path: "/leagues/{identifier}/cooldowns/issue"
tags: ["League: Moderation"]
---

# Issue a league cooldown

`POST /leagues/{identifier}/cooldowns/issue`

Issues or updates a manual cooldown for a league member. Requires a personal or developer API key whose owner is currently a league ADMIN of the league in the path, with the league cooldowns capability enabled on the key. League API access is gated at api_pro on the league owner's plan.

## Path parameters

- `identifier` string, required — League slug or Convex league ID.

## Request body

- IssueCooldownRequestBody — Issues or updates a manual league member cooldown.
  - `userId` string, required — User ID receiving the cooldown.
  - `cooldownHours` integer, required — Cooldown length in hours, from 1 to 8760.
  - `note` string — Optional admin note.

## Response `200`

The league cooldown was issued.

- IssueCooldownResponse
  - `success` true, required
  - `cooldownId` string, required — League member cooldown ID.
  - `timestamp` string, required — Response generation time (ISO 8601).

## Other responses

- `400` — Bad request (invalid body, cursor, limit, or date).
- `401` — Missing or invalid API key.
- `403` — API key lacks the required permission.
- `404` — Resource not found.
- `429` — Rate limited.
- `500` — Internal server error.

---

[API](https://skmtc.net/teambattles/apis/teambattles-api.md) · [All operations](https://skmtc.net/teambattles/apis/teambattles-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/teambattles/teambattles-api/versions/2ffe8fb53b7d/schema)