Foodzilla
New · Beta

Connect Foodzilla to the rest of your business

It's a way for the systems you already run, your website, your checkout, your CRM, to talk to Foodzilla directly. When somebody buys, cancels or upgrades on your side, their Foodzilla account keeps up on its own.

It's built for businesses selling online at some scale, rather than for coaches adding clients one at a time. Somebody (or your AI agent) needs to build the integration: it's a plain REST API, and once your key is live the full reference sits on the Integrations page, ready to hand over or paste straight into an AI assistant.

Your websiteYour checkoutYour CRMYour AI agent

What the Developer API can do

Sign members up from wherever you sell

Your website, your checkout, your booking page. When somebody joins, their Foodzilla account is created and their welcome email goes out. Nobody has to sit there adding people by hand.

  • New members land in Foodzilla within seconds of paying.
  • Works from a membership site, a course platform or your own form.
  • They count towards your plan just like any other client.
Hands off

Access that switches itself on and off

When a payment fails or somebody cancels, their access can stop the same minute. When they come back, it starts again and everything they logged before is still waiting for them.

A
A. Whitfield
Active
J
J. Moreau
Active
P
P. Nkosi
Paused
Per member

Give each member only what they paid for

Decide what every person sees. A recipes-only tier, a portal without the mobile app, or the full coaching experience. One platform, different doors.

Recipes
Portal
Recipes
Meal plans

Your client list, always in step

Read your own roster whenever your systems need it, so who's active in Foodzilla always matches who's active on your side.

One key, in your hands

Generate your key from the Integrations page, hand it to whoever's building the integration, and revoke it yourself the moment you want to.

Secure by design

Client health data stays private

Client health data is not available through the API. Goals, macros and daily logs stay between you and your client, inside the app and the client portal. Every request runs over an encrypted connection, and you can rotate or revoke your key yourself at any time, which stops it working within seconds.

GET/clients/cl_8f2a91
client_idcl_8f2a91
accessactive
Client health data
Encrypted in transitRevoke or rotate any time

Sits alongside Zapier

Already automating with Zapier? Keep it. The Developer API is there for the things Zapier can't do on its own.

Hand it to an AI and it builds it

It's a plain REST API with no surprises. Copy the whole reference from the Integrations page and give it to your developer, your agency, or an AI agent that can write the integration straight from it.

Build on top of Foodzilla

Keep your own site, your own pricing and your own tiers. Foodzilla becomes the nutrition engine behind them, and the API is the piece that joins the two together.

I'm a solo nutrition coach and Foodzilla has become the backbone of my business. What's stood out most is the support. Every time I've asked for something the team has responded quickly and actually helped, and they've been genuinely open to feedback. They've rolled out features I've asked about, which you don't often get. If you're a coach who wants to deliver meal plans and recipes properly without stitching five different tools together, it's worth a look.
TTeaganNutrition coach

What people build with it

Ways businesses wire it into what they already sell, without anyone touching a spreadsheet.

1

A recipes-only membership

Sell a lower-priced tier that's just your recipes, on your own website, at your own price.

Somebody buys your recipe membership on your site.

Their Foodzilla account is created and set to recipes only.

They sign in to the portal and see your recipes, nothing else.

2

A membership site that runs itself

Joins, cancellations and failed payments all flow through without anybody watching.

A member joins or cancels on your site.

Foodzilla adds them or pauses them straight away.

No reconciling two lists at the end of the month.

3

Tiered programmes

Bronze, silver and gold that actually behave differently inside the app.

You sell three tiers on your own checkout.

Each tier turns on a different set of features.

Upgrades take effect without a support ticket.

4

Onboarding done before the first call

New clients arrive set up, so your first session is coaching rather than admin.

A new client fills in the intake form on your website.

They're created in Foodzilla and invited automatically.

You open their record already set up and ready.

5

Your CRM stays the source of truth

For teams whose CRM, booking system or practice software already owns the client list.

Your CRM or practice system owns the client list, as it always has.

Changes there flow into Foodzilla on their own.

Your team works in one place instead of two.

6

Winning back the people who paused

Coming back should feel like picking up, not starting over.

A lapsed member resubscribes on your site.

Their old account is switched back on.

Every meal, weigh-in and note is still there.

7

Group challenges and cohorts

Run a six-week challenge where everyone starts together and access closes on the same day.

Sign-ups close on your site and the cohort is set.

Everyone is created in Foodzilla with the same setup.

When it ends, the whole group switches off in one go.

8

Workplace and corporate wellness

An employer buys nutrition for their staff, and the roster follows who actually works there.

Staff join through the employer's portal or HR system.

Each one arrives with the experience that programme includes.

When somebody leaves, their access goes with them.

9

A free taster that closes itself

Give a lead a week of limited access without committing to a full client, or to remembering to end it.

Someone claims your free trial on your website.

They get a restricted account: your recipes, nothing else.

A week later your system switches them off and frees the seat.

Availability

Included with White Label and Team plans

The Developer API is in beta. It's complimentary for customers on the White Label and Team plans, for as long as that subscription is active.

  • Generate and revoke your key yourself, from the Integrations page.
  • You'll agree to the Developer API beta terms before your key is issued.
  • It's a beta, so build it with someone who can keep an eye on it.

Frequently Asked Questions

Developer API for Nutrition & Coaching Businesses | Foodzilla