Fetch in-app notifications
Returns the authenticated user’s notification inbox. *
- Agents additionally get the All/Agent/Athletes inbox tabs (ENG-1385):
scopefilters the - list,
countscarries the per-tab totals, and every row carriesaudienceplus an identityblock for the profile picture, name and description the inbox renders. These- additions are agent-only; every other role receives the unchanged response and
scopeis - ignored for them.
- The Agent/Athletes split is derived from
athlete_idat read time and needs no stored - audience column: a row the agent owns that is about a represented athlete carries
athlete_id, a row about the agency itself leaves it null. This applies uniformly to- existing and new rows, so no backfill is involved.
countsare category totals, not unread totals. The bell indicator keeps usingunread_count, which is never scoped by the active tab.
POST
Fetch in-app notifications
Authorizations
JWT Bearer token authentication. Use the /api/login endpoint to obtain a token.
Body
application/json
Example:
1
Example:
10
Alias for limit
Example:
10
Agent inbox tab. Ignored for non-agent roles. An unrecognised value falls back to all instead of failing the request, so older clients keep working.
Available options:
all, agent, athletes Example:
"athletes"