Every API operation is reachable through a service accessor on IntervalsClient: client.athletes, client.activities, and so on. Each page below describes one service, lists its methods with links into the reference, and shows a few realistic examples. Athlete-scoped methods take an optional trailing athleteId; without it the client's configured athlete (default '0', the authenticated user) is used.