Skip to main content

Quickstart

1. Get your API key

Self-serve: sign up at saturday.fit/api for $5.39/month, no contract. Your key is revealed once after checkout and emailed to you. An AI agent can do this for you: POST /v1/signup (no auth) returns a hosted checkout link. Not sure self-serve is your lane? See Getting Access. Platform partners: keys come with your agreement. Contact api@saturday.fit. Keys carry an environment prefix. Production keys start with sk_live_, sandbox keys with sk_test_, and the two are not interchangeable: a sandbox key does not authenticate against production. See Authentication for what each environment does and which base URL it uses.
Treat your key like a password. It authenticates every request and spends your daily call allowance.
The examples below read the key from a SATURDAY_API_KEY environment variable, so the same code runs against either environment:

2. Make your first calculation

The prescription endpoint takes activity parameters and returns fuel, hydration, and sodium targets. Only activity_type and duration_min are required; everything else sharpens the result.

Install an SDK (optional)

Saturday publishes SDKs for Python and TypeScript:
Both SDKs default to https://api.saturday.fit and accept a base URL override (base_url in Python, baseUrl in TypeScript) for sandbox work.

3. Read the response

A successful response returns a prescription with safety metadata:
A response may also carry a precision object describing which profile fields are still missing and how much they widen the answer. See Onboarding for how to collect them.
Safety data is never gated. Every response carries full safety metadata regardless of subscription status, because overdrinking can cause hyponatremia, a potentially fatal condition.

4. Teaser and full responses

tier reflects the athlete’s subscription and trial status, not your key’s environment. A request with no athlete attached returns full precision. Teaser responses carry a subscription_cta field, and their attribution.required is true:
See Freemium Model for how the tiers are decided and how the subscribe loop pays you.

5. Next steps

1

Create an athlete profile

Athletes stores athlete settings (weight, sweat level, preferences) so calculations stop relying on defaults.
2

Understand safety

Safety covers the safety model and the ceilings above.
3

Track activities

Activities creates activities, attaches prescriptions, and collects post-session feedback.
4

Go to production

Authentication covers swapping a sk_test_ key and its sandbox base URL for a sk_live_ key against api.saturday.fit.