canonical: https://jentic.com/apis/nutribot.io/nutribot

# Nutribot - Zapier API

The Nutribot Zapier API exposes a small set of endpoints designed to feed customer and order events from a Nutribot meal-plan storefront into Zapier and other automation tools. It supports authenticating with a bearer token, retrieving the merchant account profile, and pulling new customer and new order records suitable for use as Zapier triggers. The surface is intentionally narrow - four operations under /admin/api - making it well suited to syncing fresh signups and orders into a CRM, email tool, or warehouse without a heavy integration build.

## For AI agents

Pull new Nutribot customers and orders for use as Zapier-style triggers, with bearer-token authentication and a single account-info call.

## Scope

Does not handle product catalogue management, payments, or shipping logistics - use for surfacing new Nutribot customer and order events only.

## Capabilities

- Authenticate to Nutribot using email and password to obtain a bearer access token
- Retrieve the authenticated merchant account profile for downstream personalisation
- Fetch newly created customers as a Zapier trigger feed
- Fetch newly placed orders as a Zapier trigger feed
- Bridge a Nutribot meal-plan store into CRM, email, or analytics workflows without bespoke code

## Use cases

### Sync New Nutribot Customers Into a CRM

Mirror every new Nutribot signup into a downstream CRM such as HubSpot or Pipedrive by polling the new-customers endpoint and forwarding records as contacts. The API returns customer records suitable for direct mapping into CRM contact fields, so a small worker can keep both systems aligned without manual exports. Typical setup time is under an hour once a bearer token is in hand.

Example prompt: Authenticate with Nutribot, call GET /admin/api/mc/zapier/new-customers, and create a HubSpot contact for each returned customer record.

### Trigger Order Notifications and Fulfilment

Use the new-orders endpoint as a poll-based trigger to notify operations staff or kick off downstream fulfilment tasks whenever a Nutribot order is placed. Each order includes the metadata needed to alert teams in Slack, write a row to a sheet, or hand off to a shipping system. This avoids the cost of building a dedicated webhook receiver while still giving near-real-time visibility into sales.

Example prompt: Poll GET /admin/api/mc/zapier/new-orders every five minutes and post a summary of any new orders to a Slack channel.

### Agent-Driven Nutribot Reporting

Let an AI agent answer ad-hoc questions about Nutribot activity - for example, how many new customers signed up this week or which orders came in overnight - by chaining the account, new-customers, and new-orders endpoints behind a single intent. Through Jentic, the agent searches by intent and gets only the operations it needs, with credentials handled by the platform.

Example prompt: Search Jentic for 'list new Nutribot orders', load the operation, and return a count of orders placed in the last 24 hours.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /admin/oauth/token | Obtain a bearer access token from email and password |
| GET | /admin/api/account | Retrieve the authenticated merchant account |
| GET | /admin/api/mc/zapier/new-customers | List new customers for Zapier triggers |
| GET | /admin/api/mc/zapier/new-orders | List new orders for Zapier triggers |

## Key resources

- **Authentication** — Exchange merchant credentials for a bearer access token via /admin/oauth/token.
- **Account** — Retrieve the authenticated merchant account profile.
- **Customers (Zapier feed)** — List newly created customers as a polling-based trigger feed.
- **Orders (Zapier feed)** — List newly placed orders as a polling-based trigger feed.

## Why Jentic

- **Setup:** Wiring the Nutribot Zapier API by hand means running the /admin/oauth/token exchange, managing the token, and handling the request plumbing against api.nutribot.io yourself. Through Jentic you install once, import Nutribot from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Nutribot event feeds carry no resource id in the path, so scope the agent to the operations it needs: you can allow surfacing new customers and new orders plus the account lookup and leave everything else out. You choose the operations it may call, so it only reaches the endpoints you list.
- **Credential handling:** Your Nutribot bearer token and underlying email and password are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list new Nutribot orders' or 'get Nutribot account', and Jentic returns the matching Nutribot operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify Admin API** — Full-featured commerce platform API with native webhooks for orders and customers, versus Nutribot's narrow Zapier feed.
- **HubSpot CRM Contacts API** — Pair with Nutribot to land new customers as HubSpot contacts and trigger downstream marketing.
- **Mailchimp Marketing API** — Push Nutribot customers into Mailchimp audiences for transactional and marketing email.

## FAQ

### What authentication does the Nutribot Zapier API use?

The API uses a bearer access token sent in the Authorization header. You exchange merchant email and password at POST /admin/oauth/token to receive the token, then attach it to every subsequent call. Through Jentic, the bearer token is held in the encrypted vault so the agent never sees the raw secret.

### Can I receive real-time push notifications from Nutribot?

No - the API exposes Zapier-style polling feeds at /admin/api/mc/zapier/new-customers and /admin/api/mc/zapier/new-orders rather than push webhooks. Schedule a regular poll on the cadence you need and treat each response as the trigger payload.

### What are the rate limits for the Nutribot Zapier API?

The OpenAPI spec does not publish explicit rate limits. Treat the polling feeds as low-frequency triggers (for example, every one to five minutes) and back off on any 429 or 5xx response.

### How do I list new Nutribot orders through Jentic?

Run pip install jentic, then search for 'list new Nutribot orders'. Jentic returns the GET /admin/api/mc/zapier/new-orders operation with its input schema; load it and execute with your stored bearer credentials. Run it through Jentic One, the self-hosted execution layer, to get an agent API key.

### Is the Nutribot Zapier API free?

Access is tied to a Nutribot merchant account; the API itself is included with the Nutribot plan and there is no separate published price list for API calls. Confirm any usage caps with your Nutribot account contact.

### Can I limit what my agent is allowed to do with the Nutribot Zapier API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use, and the Nutribot feeds carry no resource id in the path, so you scope access at the operation level. You can allow just the ones you need, such as listing new customers at GET /admin/api/mc/zapier/new-customers, listing new orders at GET /admin/api/mc/zapier/new-orders, and the account lookup at GET /admin/api/account, and leave every other endpoint out. The agent only reaches the operations you list, using the bearer token you stored, so it never touches endpoints you did not permit.