Skip to main content
POST
Get represented athletes, sending the filters in a body

Authorizations

Authorization
string
header
required

JWT Bearer token authentication. Use the /api/login endpoint to obtain a token.

Body

application/json
page
integer
Example:

1

item
integer
Example:

10

isMedia
enum<string>
Available options:
Y,
N
Example:

"Y"

isAudience
enum<string>
Available options:
Y,
N
Example:

"Y"

job_id
integer | null
Example:

2740

sort_column
enum<string>

Same as the GET. Ignored under view: removal.

Available options:
client,
profile,
tax_documents,
in_progress_deals,
earnings,
instagram,
tiktok,
twitter
Example:

"earnings"

sort_order
enum<string>
Available options:
asc,
desc
Example:

"desc"

filter
object

Keyed by column, same shapes the GET documents. Under view: removal this is what Select All means, so send the filter the grid is showing. Omitting it while a column is filtered widens the selection to the entire roster and the modal will name athletes the agent never saw.

Example:
view
enum<string>

Omit for the roster. removal returns only athlete_id, profile_photo, name and university, with no audience, social or activity data, which is what makes paging the whole selection cheap.

Available options:
removal
Example:

"removal"

is_all_selected
any

Whether Select All was used. The boolean, the strings true and 1, and the number 1 are all accepted, matching DELETE /agent/athletes.

Example:

true

excluded_athlete_id
integer[]

Athletes the agent unticked after Select All. Read only when is_all_selected is set, and taken out of meta.total as well as data, so the page count shrinks as the agent unticks.

Example:

Response

200 - application/json

Roster page. Same body as GET /agent/athletes, or the four-field removal rows under view: removal, paged the same way in either case.

data
object[]

Shown for view: removal. Without it the rows are the full roster shape.

meta
object