---
title: "Get league activity feed"
method: POST
path: "/leagues/{identifier}/activity-feed"
tags: ["League: Overview"]
---

# Get league activity feed

`POST /leagues/{identifier}/activity-feed`

Returns recent league activity entries. Requires a personal or developer API key whose owner is currently a league ADMIN of the league in the path, with leagues.league_admin:read access on the key. These admin reads no longer require a paid developer plan; they stay authority-gated (current league ADMIN) and rate-limited by the league owner's plan. League API WRITE routes still require the leagueOperatorApi feature (api_pro or higher) on the league owner's plan.

## Path parameters

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

## Request body

- LeagueActivityFeedRequestBody — Cursor pagination options for a league activity feed.
  - `limit` integer
  - `cursor` string, nullable

## Response `200`

League activity feed.

- LeagueActivityFeedResponse — A paginated league activity feed.
  - `activities` unknown[], required — Activity entries, newest first. Each carries id, action, actorId, targetType, targetId, metadata and createdAt. Normal actions include actorName; actions taken by TeamBattles Platform Staff under audited elevation suppress actorName and set isPlatformStaff: true, keeping only actorId.
    - unknown
  - `nextCursor` string, required
  - `hasMore` boolean, required
  - `timestamp` string, required

## 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/revisions/2ffe8fb53b7d/schema)