Read a represented athlete's profile
What the Edit Profile modal prefills its inputs with (ENG-1474). The counterpart to the PUT below: every field that endpoint accepts is readable here, so the modal never shows a value it cannot save back. Authorization runs through the active agent_athletes relationship, so an agent can only read an athlete on their own roster, and an athlete they do not represent is reported the same way as one that does not exist. *
- The response is the same body
POST /getAthleteDetailreturns for the athlete’s own edit screen, produced by the same resource, so both sides share one field mapping. Two names differ from the PUT: date of birth is returned asDOBand hometown aslocation. - Not returned: the athlete’s password, and nothing here lets an agent reach their login.
Authorizations
JWT Bearer token authentication. Use the /api/login endpoint to obtain a token.
Path Parameters
Athlete user id. Must be on the authenticated agent's roster.
28550
Query Parameters
Whether to include the athlete's full job history in jobs. Off by default here because the modal never shows it and it is the one field that grows without bound. The key is always present and always an array.
Response
Athlete profile