Quickstart
This guide gets you from zero to a working nutrition calculation in under 5 minutes.1. Get your API key
Contact api@saturday.fit to request a sandbox API key. Sandbox keys start withsk_test_ and work against test data with no rate limit concerns.
Sandbox keys return realistic data but never affect production athletes. Use them freely during development.
2. Make your first calculation
The core of Saturday’s API is the nutrition calculation endpoint. It takes activity parameters and returns a fuel prescription.Install an SDK (optional)
Saturday provides official SDKs for Python and TypeScript:3. Read the response
A successful response returns a fuel prescription with safety metadata:| Field | What it means |
|---|---|
tier | Response tier — "full" for subscribed athletes, "teaser" for free |
carb_g_per_hr | Carbohydrate target in grams per hour |
sodium_mg_per_hr | Sodium target in milligrams per hour |
fluid_ml_per_hr | Fluid target in milliliters per hour |
total_* | Total amounts for the entire activity duration |
safety.confidence_score | How confident Saturday is in this prescription (0.0-1.0) |
safety.warnings | Any safety warnings for this prescription |
safety.not_instructions | Signals that prescriptions are guidance, not commands |
4. Understand teaser vs. full responses
The response above shows full precision numbers because it’s from a sandbox key. In production, responses depend on the athlete’s subscription status:| Athlete status | What they get | Example |
|---|---|---|
| Subscribed | Exact numbers | "carb_g_per_hr": 62.5 |
| Free / teaser | Ranges | "carb_range_g_per_hr": "60-80" |
subscription_cta field:
5. Next steps
You’ve just calculated a nutrition prescription with minimal inputs. From here:Create an athlete profile
Athletes — Store athlete settings (weight, sweat level, preferences) for more accurate calculations.
Understand safety
Safety — Learn about Saturday’s safety model and why it matters.
Track activities
Activities — Create activities, attach prescriptions, and collect feedback.
Go to production
Authentication — Swap your
sk_test_ key for a sk_live_ key when you’re ready.