Skip to main content

Authentication and base URL

Base URL​

All endpoints are under one base URL:

https://dev.nutritionistpro.com/v3/customer

The same value is shown on the API Key card of the Settings page as API base URL.

Add the endpoint path to the base URL to build a request. For example, the recipes list is https://dev.nutritionistpro.com/v3/customer/recipes.

The API is served over HTTPS only.

Send your API key​

Send your key in the Authorization header of every request, using the Bearer scheme:

Authorization: Bearer npcust_...

A complete request with curl:

curl -H "Authorization: Bearer <API_KEY>" \
  "https://dev.nutritionistpro.com/v3/customer/labels?limit=5"

Replace <API_KEY> with the key you created on the Settings page. See Get started if you do not have one yet.

The key is accepted only in the Authorization header. It is never sent as a query parameter, which keeps it out of server logs and browser history.

What the key gives access to​

A key is tied to the user who created it. It returns what that user can see in Nutritionist Pro: their own data, plus data shared with them by other users on the same account.

An ID that belongs to another account returns 404, the same response as an ID that does not exist.

Authentication errors​

  • 401 with the message Missing API key. The request had no Authorization header, or the header did not use the Bearer scheme.
  • 401 with the message Invalid API key. The key is unknown, was revoked or replaced, or belongs to a user who is no longer active.
  • 403 with the message This account has no active subscription.. The key is valid, and the account's subscription has ended, been cancelled, or been frozen.

See Errors and limits for the full list.

Other Nutritionist Pro keys​

The customer API accepts customer API keys only. An MCP key, which begins with npmcp_, is for the MCP server and is refused here with a 401.

Caching​

Every response carries Cache-Control: no-store. Responses contain account data and should not be held in a shared cache.