> ## Documentation Index
> Fetch the complete documentation index at: https://developer.mogl.online/llms.txt
> Use this file to discover all available pages before exploring further.
# Get the activity feed (comments + activity logs) for a file slot
> Returns a paginated activity feed for a file slot, newest first (sorted by `created_at` desc, then `id` desc so bursts in the same second keep a stable order). Comments and activity logs are merged into one list — each item is tagged with type (`comment` or `log`). The caller's read-state is also updated: brand reads mark non-brand comments as partner-read; athlete/agent reads mark brand comments as athlete-read. The top-level data.comment_count field is the total number of comments (excluding activity logs).
Example: /deal-folder/files/23/comments?page=1&limit=10.
## OpenAPI
````yaml /storage/api-docs/api-docs.json get /deal-folder/files/{file}/comments
openapi: 3.0.0
info:
title: MOGL Core API
description: >-
MOGL Platform Core API — powering athlete NIL deals, brand partnerships,
agent management, payments, messaging, and more.
*
* ## Authentication
* - **JWT Bearer Token**: Most endpoints require a Bearer token obtained via `/api/login`.
* - **Server-to-Server API Key**: Internal/lambda/cron endpoints use an `X-API-KEY` header.
*
* ## Rate Limiting
* - Registration & login endpoints: 4–15 requests per minute
* - Public/influencer endpoints: 200 requests per minute
* - Authenticated endpoints: standard Laravel throttle
version: 1.0.0
servers:
- url: http://localhost/mogl/mogl-backend/api
description: Local
- url: https://dev-api.mogl.online/api
description: Dev
- url: https://staging-api.mogl.online/api
description: Staging
- url: https://api.mogl.online/api
description: Production
security:
- bearerAuth: []
tags:
- name: Authentication
description: Login, registration, password reset
- name: User Registration - Common
description: Common user registration & email check
- name: User Registration - Athlete
description: Athlete registration & onboarding steps
- name: User Registration - Partner
description: Partner/Brand registration & onboarding steps
- name: User Registration - Agent
description: Agent registration & onboarding steps
- name: User Registration - Fan
description: Fan registration & onboarding steps
- name: User Profile
description: User profile management, settings, social media
- name: Athlete
description: 'Athlete-specific endpoints: search, details, availability'
- name: Athlete - Availability Confirmation
description: Post-hiring availability confirmation workflow
- name: Athlete - NIL Feed
description: Athlete NIL feed and partner search
- name: Athlete - AI Assistant
description: AI-powered job assistant for athletes — chat and conversation history
- name: Partner
description: Partner/Brand-specific endpoints
- name: Partner - External Job
description: External job link & applicant management
- name: Partner - Deliverable Report
description: Deliverable detail reports for brands
- name: Partner - Screening Questions
description: Screening question reports
- name: Partner - Contract Management
description: Brand contract management with athletes
- name: Partner - Content Library
description: Brand content library for deliverable assets
- name: Agent
description: Agent profile, athlete management, contracts
- name: Agent - Athletes
description: Agent-athlete relationship management
- name: Agent - Stripe
description: Agent payment methods & billing via Stripe
- name: Agent - Contracts
description: Agent athlete contract management
- name: Agent - Availability Confirmation
description: Agent managing athlete job availability
- name: Jobs
description: Job/deal CRUD, search, invitations, hiring, deliverables
- name: Deals
description: Deal listing, my deals, bulk operations
- name: Deal Folder
description: >-
Deal folder file workflow — uploads, replacements, approvals, revisions,
comments. Accessible by athlete, partner/brand, agent, and iOS clients
(per-action authorisation enforced server-side).
- name: Deal Folder iOS API
description: >-
iOS-only direct-to-S3 multipart upload endpoints for deal folder files
(initiate/complete for new uploads and replacements). Web clients should
use the standard `Deal Folder` upload/replace endpoints instead.
- name: Chat
description: Messaging, chat contacts, notifications
- name: Notifications
description: Notification preferences, in-app notifications
- name: Payments
description: Stripe payments, payment history, cards, bulk pay
- name: Subscription
description: Brand subscription plans & management
- name: Public Pages
description: Public content endpoints (no auth required)
- name: Public - Influencer/SEO
description: Public influencer discovery, sitemaps, directories
- name: Services
description: Athlete service marketplace
- name: iOS Device
description: iOS device tokens, live activities
- name: Onboarding Tutorial
description: Onboarding tutorial progress
- name: MOGL Rosters
description: Roster management & display
- name: Internal / Cron
description: Server-to-server and cron job endpoints
- name: Affiliate
description: Athlete affiliate links & tracking
paths:
/deal-folder/files/{file}/comments:
get:
tags:
- Deal Folder
summary: Get the activity feed (comments + activity logs) for a file slot
description: >-
Returns a paginated activity feed for a file slot, newest first
(sorted by `created_at` desc, then `id` desc so bursts in the same
second keep a stable order). Comments and activity logs are merged into
one list — each item is tagged with type (`comment` or
`log`). The caller's read-state is also updated: brand reads mark
non-brand comments as partner-read; athlete/agent reads mark brand
comments as athlete-read. The top-level data.comment_count
field is the total number of comments (excluding activity
logs).
Example:
/deal-folder/files/23/comments?page=1&limit=10.
operationId: getDealFolderFileComments
parameters:
- name: file
in: path
description: DealFolderFile ID (slot ID).
required: true
schema:
type: integer
example: 5
- name: page
in: query
description: Page number (1-indexed).
required: false
schema:
type: integer
example: 1
- name: limit
in: query
description: Items per page (default 10).
required: false
schema:
type: integer
example: 10
responses:
'200':
description: Paginated activity feed
content:
application/json:
schema:
properties:
status:
type: string
example: success
data:
properties:
current_page:
type: integer
example: 1
last_page:
type: integer
example: 3
per_page:
type: integer
example: 10
total:
type: integer
example: 27
comment_count:
description: >-
Total number of comments only (excludes activity
logs).
type: integer
example: 18
data:
type: array
items:
properties:
id:
type: integer
example: 300
type:
type: string
enum:
- comment
- log
example: comment
comment:
description: Present when type='comment'.
type: string
example: Looks great!
nullable: true
user:
description: Present when type='comment'.
properties:
id:
type: integer
example: 42
name:
type: string
example: Jane Doe
profile_photo:
type: string
nullable: true
role_id:
type: integer
example: 2
user_type:
type: string
enum:
- Partner
- Athlete
- Agent
- Fan
- Unknown
example: Athlete
type: object
nullable: true
event_type:
description: >-
Present when type='log' (DealFolderEventType
value).
type: string
example: FILE_UPLOADED
nullable: true
performed_by:
description: Present when type='log'.
properties:
id:
type: integer
example: 42
name:
type: string
example: Jane Doe
type: object
nullable: true
on_behalf_of:
description: >-
Present when type='log' and an agent acted on
behalf of an athlete.
properties:
id:
type: integer
example: 42
name:
type: string
example: Jane Doe
type: object
nullable: true
created_at:
type: string
format: date-time
example: '2026-04-01T13:00:00Z'
type: object
type: object
type: object
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/UnauthorizedResponse'
'403':
description: Access denied
content:
application/json:
schema:
properties:
status:
type: string
example: error
message:
type: string
example: Access denied.
type: object
'404':
description: Deal folder file not found
content:
application/json:
schema:
properties:
status:
type: string
example: error
message:
type: string
example: Deal folder file not found.
type: object
security:
- bearerAuth: []
components:
schemas:
UnauthorizedResponse:
properties:
message:
type: string
example: Unauthenticated.
type: object
securitySchemes:
bearerAuth:
type: http
description: >-
JWT Bearer token authentication. Use the /api/login endpoint to obtain a
token.
scheme: bearer
bearerFormat: JWT
````