[Cotlet](https://cotlet.dev/index.md) · [All integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Create your own Cronometer API

> Cronometer: the API is for partner platforms, not for your own account. With Cotlet you build your own: do a job once with your AI agent, save it as an endpoint and call it from n8n or code.

Source: https://cotlet.dev/integrations/api/cronometer

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.

[Try it free now](https://cotlet.dev/app/signup?app=cronometer)

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 Node.js Python

curl

```
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"}'
```

Node.js

```
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();
```

Python

```
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"]
```

Response 200 OK · JSON

```
{
"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?

1. 01  
cronometer.com  
Signed in  
### Sign in to Cronometer in your Cloud Browser.  
You type your password yourself. Cotlet keeps the signed-in session, encrypted, never the password.
2. 02  
Read my diary for a week and give energy, protein and fiber for each day.  
### Do the job once with your agent.  
For example: "Read my diary for a week and give energy, protein and fiber for each day."
3. 03  
Save endpoint  
Name  
nutrients-for-week  
Input  
from, to  
Returns  
day, energy\_kcal, protein\_g, fiber\_g  
### 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.
4. 04  
$ POST /api/v1/custom/nutrients-for-week  
200 OK  
### Call it with your Cotlet API key.  
Each endpoint gets its own address, `POST https://cotlet.dev/api/v1/custom/<name>`. You send JSON in and get JSON back, from the same signed-in Cronometer session.

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/log-food` writes  
### Log a food  
A food with its amount, in the meal you name
- POST `/api/v1/custom/<name>`

A call to an endpoint you built could look like this:

Request

```
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`:

Response · 200 OK

```
{
"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.

DRY RUN · nothing sent

$ POST /api/v1/custom/log-food

would POST cronometer.com/... log 150 g grilled chicken to lunch

`log-food`writes

Allow writes

Daily cap 20 writes

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?](https://cotlet.dev/api-status/cronometer.md)

Want ChatGPT or Claude to work in Cronometer instead of code? See the [Cronometer MCP server](https://cotlet.dev/integrations/mcp/cronometer.md).

0/3

Official API

Partners only

[Full API & MCP report](https://cotlet.dev/api-status/cronometer.md)

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.

POST /api/v1/custom/<name>

## Build your first Cronometer endpoint

Sign in once, do the job with your agent and save it as an endpoint.

[Try it free now](https://cotlet.dev/app/signup?app=cronometer)

No card. Takes about 5 minutes.

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [MCP servers](https://cotlet.dev/integrations/mcp.md) · [APIs](https://cotlet.dev/integrations/api.md) · [API & MCP status](https://cotlet.dev/api-status.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md) · [Custom API](https://cotlet.dev/custom-api.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. [About us](https://cotlet.dev/about.md)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.
