Cronometer API · unofficial, by Cotlet
Create your own Cronometer API
Cronometer: no API for your own account found; Cronometer's API is for partner platforms such as Everfit (checked 20 Nov 2026). With Cotlet you can build your own. Do a job once with your AI agent in your Cronometer account, save it as an endpoint, and call it from n8n, Make, Zapier or your own code. Each endpoint runs in your own signed-in Cronometer session and returns only what your login can see.
Free 7-day trial, 2,000 credits, no card
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by Cronometer. Cronometer is a trademark of its owner. If Cronometer's own integrations cover what you need, use them first.
curl -X POST "https://cotlet.dev/api/v1/custom/nutrients-for-week" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-14", "to": "2026-11-20"}' const url = "https://cotlet.dev/api/v1/custom/nutrients-for-week";
const res = await fetch(url, {
method: "POST",
headers: {
Authorization: `Bearer ${process.env.COTLET_API_KEY}`,
"Content-Type": "application/json",
},
body: JSON.stringify({ from: "2026-11-14", to: "2026-11-20" }),
});
const { data } = await res.json(); import os
import requests
key = os.environ["COTLET_API_KEY"]
res = requests.post(
"https://cotlet.dev/api/v1/custom/nutrients-for-week",
headers={"Authorization": f"Bearer {key}"},
json={"from": "2026-11-14", "to": "2026-11-20"},
)
data = res.json()["data"] {
"data": [
{
"day": "2026-11-19",
"energy_kcal": 1980,
"protein_g": 104,
"fiber_g": 22
},
{
"day": "2026-11-20",
"energy_kcal": 1240,
"protein_g": 62,
"fiber_g": 18
}
]
} 01 Build
How do you build a Cronometer endpoint with Cotlet?
-
Sign in to Cronometer in your Cloud Browser.
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
-
Do the job once with your agent.
For example: "Read my diary for a week and give energy, protein and fiber for each day."
-
Save it as an endpoint.
Give it a name, choose its inputs, such as a date range or a nutrient, and the fields it returns.
-
Call it with your Cotlet API key.
Each endpoint gets its own address,
POST https://. You send JSON in and get JSON back, from the same signed-in Cronometer session.cotlet.dev/ api/ v1/ custom/ <name>
02 Endpoints
Example endpoints you could build for Cronometer
Cotlet ships no fixed list of Cronometer endpoints. You decide which endpoints you build and what each one returns.
-
POST
/api/v1/custom/nutrients-for-week Nutrients for a period
Energy, protein, fiber and other nutrients per day
-
POST
/api/v1/custom/diary-for-day The diary for a day
Each food logged, with amount and meal
-
POST
/api/v1/custom/under-target Nutrients under target
Nutrients below your target, and on how many days
-
POST
/api/v1/custom/biometrics Biometrics for a period
Weight and other entries you logged
-
POST
/api/v1/custom/writeslog-food Log a food
A food with its amount, in the meal you name
A call to an endpoint you built could look like this:
curl -X POST "https://cotlet.dev/api/v1/custom/nutrients-for-week" \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"from": "2026-11-14", "to": "2026-11-20"}' The answer is JSON, with your fields under data:
{
"data": [
{
"day": "2026-11-19",
"energy_kcal": 1980,
"protein_g": 104,
"fiber_g": 22
},
{
"day": "2026-11-20",
"energy_kcal": 1240,
"protein_g": 62,
"fiber_g": 18
}
]
} When you save an endpoint, Cotlet gives you its curl example and an OpenAPI description to paste into n8n, Make or your code.
03 Uses
What can you use your Cronometer endpoints for?
- Sunday Cotlet endpoint Email
A weekly summary.
Your week of nutrients, sent to your email on Sunday.
- Daily endpoint Google Sheets
A sheet of your own.
Daily energy and protein pulled into Google Sheets.
- Phone shortcut endpoint diary
A shortcut on your phone.
One tap that logs your usual breakfast.
- Chat agent endpoint diary
Your own nutrition assistant.
A chat agent that reads your week before it suggests a meal.
04 Access
What can an endpoint see and change?
An endpoint works in your own Cronometer session, so it can read and change only what your Cronometer login can. You choose what each endpoint does when you build it.
An endpoint that changes something, such as logging a food, first runs as a dry run: Cotlet shows you each request it would send, and nothing is sent. You allow the writes once in the Cotlet console and set a daily cap. A call over the cap fails whole, never half done.
05 Official API
Does Cronometer have an official API?
Cronometer: its Pro FAQ names Everfit, Kalix and Practice Better as platforms with access to its API, and no API for your own account was found (checked 20 Nov 2026). Diary entries and nutrition summaries export as a CSV file from Account settings. The full picture with sources: Does Cronometer have an API or MCP server?
Want ChatGPT or Claude to work in Cronometer instead of code? See the Cronometer MCP server.
06 Pricing
What does it cost?
- per successful call
- 10 credits
- when a call fails
- 0
- in the smallest pack
- ≈ 500 calls
- free trial, no card
- 7 days
A call to your endpoint costs 10 credits when it succeeds and nothing when it fails, with no browser minutes on top. Credits come in one-time packs from $29 for 5,000 credits, so a pack covers about 500 successful calls. The free trial gives you 2,000 credits for 7 days, no card.
Cronometer API with Cotlet: questions
Is this an official Cronometer API?
No. Cotlet is independent and not affiliated with Cronometer. The endpoints you build run in your own signed-in Cronometer account.
Do I need to code?
Not to build an endpoint: you do the job once with your agent and save it. To call it, you need a tool that sends HTTP requests, such as n8n, Make, Zapier or a script.
What happens when Cronometer changes its screens?
An endpoint works while Cronometer works the way it did when you built it. If Cronometer changes and a call fails, you get an email. After 3 failures in a row the endpoint turns off until you rebuild it with your agent or in the console. A failed call costs nothing.
How long can a call take?
Up to 90 seconds, and the answer can be up to 1 MB of JSON.
Build your first Cronometer endpoint
Sign in once, do the job with your agent and save it as an endpoint.
Try it free nowNo card. Takes about 5 minutes.