Skip to main content
POST
/
leagues
/
{identifier}
/
cooldowns
/
{cooldownId}
/
clear
curl -X POST https://teambattles.gg/api/v1/leagues/my-league/cooldowns/jh7cooldown123/clear \
  -H "Authorization: Bearer tb_your_api_key"

{
  "success": true,
  "timestamp": "<string>"
}

​
Permission Required

This endpoint requires a league-operator API key bound to this league with the cooldowns league capability, plus the leagueOperatorApi plan feature (api_pro or higher). A free key receives 403 error_api_feature_required.

​
Access / Membership Rules

You must have a MANAGER or higher role in the league (or be a TeamBattles staff member) to clear a cooldown. If you lack the required access, you’ll receive a 403 error. The {identifier} path parameter is the league slug - the URL-friendly league name (e.g., my-league). The cooldown referenced by {cooldownId} must belong to the bound league.

​
What’s Returned

Clears an active league member cooldown early. This endpoint takes no request body. On success the response is { "success": true, "timestamp": "<ISO 8601>" }. 
curl -X POST https://teambattles.gg/api/v1/leagues/my-league/cooldowns/jh7cooldown123/clear \
  -H "Authorization: Bearer tb_your_api_key"

Authorizations

​
Authorization
string
header
required

Send your API key as: Authorization: Bearer tb_

Path Parameters

​
identifier
string
required

League slug or Convex league ID.

​
cooldownId
string
required

League member cooldown ID.

Response

The league cooldown was cleared.

​
success
boolean
required
​
timestamp
string
required

Response generation time (ISO 8601).