Vekta API

The Vekta API lets you access your training data, and the data of the athletes you coach, from outside the Vekta app. Use it to build your own dashboards, run custom analysis, or connect Vekta to AI assistants.

The Vekta API lets you query your Vekta data directly from your own tools, scripts or spreadsheets. It is available to coaches and self-coached athletes.

What you can access depends on your role:

• Your own data: always available, using the special value me.

• Your athletes' data: available for every athlete in a Workspace where you are a Coach or an Admin.

Learn more about Workspace roles here.

The API is currently read-only, with one exception: you can invite athletes and coaches to a Workspace. You can't create or edit sessions, notes or events through the API.

• Athletes: the list of athletes you coach, with the ids you need to query their data.

• Profiles: name, date of birth, gender, height and the latest value of each metric, such as weight or critical power.

• Activities: session summaries, including laps recorded by the device, pool lengths for swimming, and laps and climbs detected by Vekta for cycling.

• Streams: the full recorded data of an activity, such as power, heart rate, cadence, speed, altitude and GPS position. Sensor data from CORE, Tymewear or Flowbio is included when it was recorded.

• Training Prescriptions: planned workouts, including their structure, targets and carbohydrate intake.

• Notes: notes on the Calendar. A note hidden until a future date is only returned to the person who wrote it.

• Events: planned events and races.

• Metrics: the full history of body and performance metrics. Each value shows whether it was entered by the user or estimated by Vekta.

• Sleep: nights recorded by connected devices such as Garmin, Oura or WHOOP.

• Workspace Invitations: invite someone to a Workspace as an athlete or a coach. You can optionally have Vekta email them the invitation code.

API keys are issued by the Vekta team.

Request a key
Contact us at support@joinvekta.com and tell us which Vekta account the key is for.

Keep it private
Your key gives access to your data and your athletes' data, so treat it like a password. Don't share it or include it in code you publish. If you think your key has been exposed, contact us straight away.

Learn more about how we protect your data in Data Privacy.

Every request goes to https://api.joinvekta.com, with your key sent as a bearer token.

Check your key
Fetch your own profile to confirm everything works:

curl https://api.joinvekta.com/users/me \
  -H "Authorization: Bearer vk_..."

Your profile also lists your Workspaces and their ids, which you need to send invitations.

List your athletes
Call GET /users to get the athletes you coach. Each athlete has an id starting with usr_, which you use in your other requests.

Query their data
Replace me with an athlete's id to fetch their data. Most lists accept an optional date range, for example:

curl "https://api.joinvekta.com/users/usr_.../activities?from=2026-08-01&to=2026-08-31" \
  -H "Authorization: Bearer vk_..."

To get the full recorded data of a session, use its activity id (starting with act_) with GET /activities/{activityId}/streams.

To keep the API fast for everyone, requests are limited:

• Per API key: 300 requests per minute, across all endpoints.

• Per athlete: 30 requests per minute for each athlete you query. Limits are tracked separately for each athlete, so you can fetch several athletes in parallel.

If you go over a limit, the API responds with a 429 error. The response includes a Retry-After header telling you how many seconds to wait before trying again.

The API is described in an OpenAPI specification, available at https://api.joinvekta.com/openapi.json. Point your AI assistant or code generator to it, and it can see every available endpoint and field.

The complete reference for every endpoint and field is available at docs.joinvekta.com. For questions or feedback about the API, contact us at support@joinvekta.com.