API documentation

Build health apps on the ClapDiet API — a REST interface over lab analysis, food data, and personalized nutrition recommendations.

Quick start

1. Request access

The ClapDiet API is in limited access and is not yet self-serve: there is no key to generate in your account settings. Write to us and we will set up your credentials.

2. Authenticate your request

Send your token in the Authorization header of every request. For example:

curl -X GET https://api.clapdiet.com/api/v1/foods \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json"

3. Handle the response

Every response is JSON. Check the status code: 200 means success, while 400 and 500 codes mean something went wrong.

Authentication

The ClapDiet API authenticates with Bearer tokens. Include yours in the Authorization header of every request.

Important: Never share your token or place it in client-side code where others can read it. Keep it on your server.

Endpoints

POST/api/v1/auth/registerCreate a new user account

POST/api/v1/auth/loginSign in and receive access tokens

GET/api/v1/labsList a user’s lab results

POST/api/v1/labs/uploadUpload new lab results (PDF or image)

GET/api/v1/foodsSearch the food database

GET/api/v1/recommendationsGet personalized food recommendations

Rate limits

To keep the API fast and fair for everyone, requests are capped in three overlapping windows. All three apply at once.

per second

per 10 seconds

100

per minute

These are the defaults the service ships with; an operator can tighten them.

Need help?

Our team is here to help you build with the API.

Contact support