canonical: https://jentic.com/apis/nutribot.com/nutribot # Nutribot - Zapier API Jentic publishes the only available OpenAPI specification for Nutribot - Zapier API, keeping it validated and agent-ready. Nutribot is a meal-plan and nutrition commerce platform whose Zapier-facing API exposes account information, new-customer events, and new-order events to power lightweight integrations. The API uses an OAuth2 token endpoint to authenticate, then surfaces account, customer, and order endpoints scoped under /admin/api/mc/zapier. It is used by Nutribot operators that want to fan customer and order events into Zapier-style automations without writing webhook handlers. ## For AI agents Authenticate as a Nutribot admin, fetch account info, and pull new customers and orders for downstream automation. ## Scope Does not handle product catalog management, payments, or kitchen scheduling - use for Nutribot Zapier-style new-customer and new-order polling only. ## Capabilities - Authenticate as a Nutribot admin via OAuth2 password grant - Retrieve the authenticated admin's account information - List new customers added since the last poll - List new orders placed since the last poll - Feed new-order events into a downstream order management workflow - Trigger Zapier-style automations from new Nutribot customer signups ## Use cases ### New-Customer Automation Nutribot operators poll GET /admin/api/mc/zapier/new-customers on a schedule and pipe each new signup into welcome-email sequences, CRM creation, and onboarding tasks. The endpoint returns a list of customers added since the last poll, making it cleanly diff-able without webhooks. Example prompt: Call GET /admin/api/mc/zapier/new-customers, then create a CRM contact for each entry returned ### Order Fulfilment Trigger Operations teams pull GET /admin/api/mc/zapier/new-orders to drive fulfilment, kitchen prep, and accounting downstream of a Nutribot order. Each pulled order can be acknowledged in the external system before the next poll, giving idempotent processing. Example prompt: Call GET /admin/api/mc/zapier/new-orders, then push each order into the kitchen prep system and mark it processed ### Agent-Driven Daily Sync An AI agent runs a daily sync that authenticates against Nutribot, pulls new customers and orders, and posts a summary to the operator's chat channel. Through Jentic the agent searches for 'new Nutribot orders', loads the schema, and executes the call without writing OAuth or polling code. Example prompt: Search Jentic for 'list new Nutribot orders', load the schema for GET /admin/api/mc/zapier/new-orders, and execute as part of a daily run ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | /admin/oauth/token | User login and token issuance | | GET | /admin/api/account | Get user account | | GET | /admin/api/mc/zapier/new-customers | List new customers | | GET | /admin/api/mc/zapier/new-orders | List new orders | ## Key resources - **Authentication** — Exchange admin credentials for a bearer access token - **Account** — Retrieve admin account information - **Customers** — List new customers for downstream automation - **Orders** — List new orders for downstream automation ## Why Jentic - **Setup:** Wiring the Nutribot Zapier API by hand means running the /admin/oauth/token exchange, refreshing the bearer token, and handling the request plumbing against api.nutribot.com 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 polling feeds carry no resource id in the path, so scope the agent to the operations it needs: you can allow the new-customers and new-orders reads and 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 credential and bearer token 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 'fetch Nutribot account info', 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 - **Square** — Commerce platform with full product, order, and customer APIs - **Trello** — Boards and cards for fulfilment workflows downstream of Nutribot orders - **Asana** — Task management for kitchen and ops teams handling Nutribot orders ## FAQ ### Why is there no official OpenAPI spec for Nutribot - Zapier API? Nutribot does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Nutribot - Zapier API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Nutribot Zapier API use? The spec declares an HTTP bearer scheme. Tokens are issued by POST /admin/oauth/token in exchange for admin credentials. Through Jentic the credentials and resulting token are stored encrypted in the vault and refreshed transparently. ### Can I list new customers added since my last poll? Yes. GET /admin/api/mc/zapier/new-customers returns customers added since the previous poll, which is the pattern Zapier and Make rely on. Use this in place of a webhook subscription. ### How do I retrieve new orders through Jentic? Search Jentic for 'list new Nutribot orders', load the schema for GET /admin/api/mc/zapier/new-orders, and execute on your polling schedule. Jentic injects the bearer token from the vault and returns the parsed order list. ### What are the rate limits for the Nutribot Zapier API? Rate limits are not declared in the OpenAPI spec. Nutribot applies internal limits suitable for Zapier-style polling intervals; keep polling at sensible cadences (every few minutes rather than every second) to stay within them. ### Does this API let me create or update customers? No. The four endpoints in this spec are read-only feeds plus authentication. Creating or updating customers and orders happens inside the Nutribot admin UI or through other internal Nutribot interfaces not exposed here. ### Can I limit what my agent is allowed to do with the Nutribot Zapier API? Yes. Jentic One runs self-hosted, so you decide which Nutribot operations your agent may call and which credential it may use. Because the polling feeds carry no resource id in their paths, you can allow just the new-customers and new-orders reads and the account lookup while leaving every other endpoint out. The agent can only reach the operations you list, and its bearer token stays under your control rather than being handed to the agent directly.