---
title: "Get locker room posts"
method: GET
path: "/api/locker-room"
tags: ["Locker room"]
---

# Get locker room posts

`GET /api/locker-room`

## Request

- Base URL: `https://app.d-sports.org`
- URL: `https://app.d-sports.org/api/locker-room`
- Auth: one of:
  - none
  - HTTP bearer

Page mode (default): `page` + `hasMore`. Cursor mode (DSE-369): pass opaque `cursor` from a prior `nextCursor`; response includes `nextCursor` (`null` at end). Both modes return `nextCursor` (#689) — a page-1 request has no cursor to send, so page mode is where a client obtains its first one; the only exception is a viewer whose filter was remapped by #614, where a cursor would 400 on the next request and is withheld. Invalid cursor → 400 (decoded against the request filter before any #614 remap). Cursors are scope-keyed (#660): a cursor issued for one `teamId` / `phase` / `postType` / `authorTeamId` / `authorId` / `includeDemo=false` scope 400s when resumed under another scope — always restart from page 1 when the scope changes. Filters: trending|latest|following|foryou. `teamId` narrows to the per-team feed (about-tagged OR authored-as for that team); `authorTeamId` narrows to officially-as-team posts; both compose with `following` as AND. NULL-matches-any: rows with unset `channel` / `teamId` match any `phase` / `teamId` filter, so untagged posts stay in scoped feeds. When the viewer has UserSettings.analyticsPersonalization=false (#614), trending/foryou are served chronological (`latest` order) and a *valid* ranked cursor is dropped after that 400-check. Ranked filters (trending/foryou) additionally carry `rank` (absolute 0-based position, continuing across pages) and `reason` ({ code, label?, subjectId? }) per post, plus `rankVersion` on the envelope (#686) — chronological filters and opted-out viewers carry none of the three. `ads` is `[]` only when inventory is switched off; an opted-out viewer takes the contextual fill path (#687). Feed preferences (#722) are applied for the authenticated viewer on every filter, including when analyticsPersonalization is false: kind `never` excludes matching authors, teams (`teamId` or `authorTeamId`), topics (`channel`), and item types at candidate generation; kind `less` downweights matching posts to one quarter of their reaction count while scoring trending/foryou and does not remove them from chronological feeds. Promoted creatives are not filtered here. Team-news rail (#827): the first page of a team-scoped feed (`teamId` or `authorTeamId` set, no `cursor`, page 1, no `authorId` filter) also carries up to 5 published articles as `data.news` (same fields as GET /api/news items plus `itemType: "news"`). Never present on the global/all feed, later pages, or cursor resumes; omitted (not empty) when there is no news or the news read fails. Each post includes `mentions` (#953): `{ id, handle, name?, profileUrl? }[]`, empty when nobody is tagged. Users the viewer has blocked (either direction) and users with a null handle are omitted.

## Query parameters

- `page` integer
- `limit` integer
- `cursor` string
- `filter` 'trending' | 'latest' | 'following' | 'foryou'
- `includeDemo` boolean
- `authorId` string
- `authorTeamId` string
- `teamId` string
- `phase` 'pre' | 'live' | 'post'
- `postType` 'standard' | 'hottake'

## Response `200`

{ success, data: { posts, hasMore, nextCursor?, rankVersion? } } — posts on ranked filters also carry `rank` and `reason` (#686)

## Other responses

- `400`: Invalid cursor — malformed, filter mismatch, or scope mismatch (teamId/phase/postType/authorTeamId/authorId/includeDemo changed between pages). Restart from page 1. A cursor whose anchor post was deleted or aged out of the ranking window is NOT a 400: the ranked filters resume from the anchor's own sort position instead. (VALIDATION_ERROR)

## Changes

- **2026-09-24** `01971acf764b`: 3 info
  - added the new optional `query` request parameter `phase`
  - added the new optional `query` request parameter `postType`
  - added the new optional `query` request parameter `teamId`
- **2026-09-12** `1d9b79112341`: 1 info
  - the endpoint scheme security `bearerAuth` was added to the API
- **2026-09-12** `a8df6fe04343`: 3 info
  - added the new optional `query` request parameter `cursor`
  - added the new enum value `foryou` to the `query` request parameter `filter`
  - added the non-success response with the status `400`
- **2026-08-26** `59a3c711262f`: 1 info
  - added the new optional `query` request parameter `authorTeamId`
- **2026-08-16** `16bfbac187d7`: 2 info
  - added the new optional `query` request parameter `authorId`
  - added the new optional `query` request parameter `includeDemo`

[Operation history](https://skmtc.dev/d-sports-ecosystem/apis/d-sports-api/changes/api/locker-room/get.md)

---

[API](https://skmtc.dev/d-sports-ecosystem/apis/d-sports-api.md) - [All operations](https://skmtc.dev/d-sports-ecosystem/apis/d-sports-api/llms.txt) - [OpenAPI document](https://skmtc.dev/d-sports-ecosystem/apis/d-sports-api/revisions/63735cf90a04?raw)
