Get locker room posts
Changed onPage 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.
Request
- Base URLhttps://app.d-sports.org
- Auth
- none
- or HTTP bearer
Query parameters
Opaque pagination cursor from a previous nextCursor. When set, takes precedence over page. Invalid, or issued for a different filter/scope (teamId/phase/postType/authorTeamId/authorId/includeDemo) → 400.
When set, only return this author's personal posts. Posts they wrote in a team voice (authorTeamId set) are excluded; fetch those with authorTeamId. Combining authorId with authorTeamId returns no rows.
When set, only return posts authored officially by this team
Per-team feed scope: posts about-tagged with this team, posts authored as this team, plus untagged (NULL teamId) posts per the NULL-matches-any rule. Composes with following as AND.
Game-phase scope (pre|live|post), matched against the post channel. Unset channel matches any phase per the NULL-matches-any rule. Unknown values are ignored.
Post-type filter (standard|hottake). hottake matches posts with isHotTake or postType=hottake; standard excludes them. Unknown values are ignored.
Response
{ success, data: { posts, hasMore, nextCursor?, rankVersion? } } — posts on ranked filters also carry rank and reason (#686)
Changes
- info
added the new optional
queryrequest parameterphase - info
added the new optional
queryrequest parameterpostType - info
added the new optional
queryrequest parameterteamId
- info