WhatsApp API for AI App Builders and No-Code Tools
Every app builder can call a REST API from server code. Only some can use an MCP connector, and often only while you build. Here is the route for each one, with the vendor docs behind it.
Daniel Roth9 min read

On this page
Short answer: The route that works in every builder is a REST call from server-side code: POST https://api.blueticks.co/v1/scheduled-messages/{chatId} with an Authorization: Bearer bt_live_... header, and the key kept in the builder's secret store. The Blueticks MCP connector is the second route, but builders that support custom MCP mostly use it inside their own chat while you build, not inside the app you ship. The messages go out from your own WhatsApp number, not from the Meta Cloud API.
This is the hub for the tool-specific guides. Two have their own post: apps built with ChatGPT and Bubble. The Blueticks side was checked against the backend and the OpenAPI spec on 2026-11-22. The builder side comes from each vendor's own documentation, linked per section. Builders change plans and menus often, so treat the docs as the final word.
What is the one recipe that works everywhere?
Three steps, the same for every tool:
- Create a key. On the API page of the dashboard, app.blueticks.co/blueticks-api. It starts with
bt_live_. Keep Full access (the default), because a Read-only key gets a403on sends. - Link a WhatsApp number.
GET /v1/pingreturnsapi: "ok"and awhatsappConnectionslist. An empty list means nothing is connected. - Send from the server. The recipient goes in the path. It can be a phone number like
+15551234567or a group id ending in@g.us:
// server code only: a function, route or backend workflow
const res = await fetch(
`https://api.blueticks.co/v1/scheduled-messages/${encodeURIComponent(chatId)}`,
{
method: "POST",
headers: {
Authorization: `Bearer ${process.env.BLUETICKS_API_KEY}`,
"Content-Type": "application/json",
"Idempotency-Key": messageUniqueId, // reuse it on a retry
},
body: JSON.stringify({ type: "text", text: "Order 4182 is packed." }),
},
);Leave out sendAt and it sends now. A 201 means sent. A 202 means WhatsApp had not confirmed in about 50 seconds, and you check the statusUrl instead of sending again. The Idempotency-Key header (up to 64 characters) makes a retry safe.
Limits to know while you prototype: an account with no active subscription gets 5 API requests per six-hour window, shared with the MCP connector. Sends are limited to 60 per minute per key, and a 429 carries Retry-After.
For replies coming back into your app, register a webhook rather than polling. That is covered in WhatsApp webhooks and auto-reply. The receiving end has to be a public URL your app can serve, so it matters which builder gives you backend routes.
Why must the key stay out of the browser?
The key can send as you and add people to your groups. Anything a browser can read is a leak. Every builder below has a server-side place for secrets, and the sections point to it. If a tool only offers a client-side call, put a small server in between.
When does the MCP connector fit instead?
The hosted connector is https://api.blueticks.co/mcp, and it signs in with OAuth. Use it when a person wants an AI to read and act on their own chats, for example "draft replies to everyone waiting on me". Use REST when your app needs deterministic sends on a schedule or a trigger. The tools are listed in WhatsApp MCP tools, and the protocol basics in the WhatsApp MCP guide.
One detail matters across builders: where a builder lets you add an MCP server, check whether it can be used by the finished app or only by the builder's own AI. The answers differ, and they are below.
ChatGPT-built apps
ChatGPT is two cases, and they get mixed up.
An app ChatGPT writes for you. That is plain REST, and the hosting you choose holds the key. The ChatGPT guide has a prompt to paste that lists the four group and send endpoints, so the model does not invent one.
ChatGPT itself operating WhatsApp. Add a custom MCP server on chatgpt.com/plugins. OpenAI's docs say to enter the server URL including the /mcp path (OpenAI MCP docs). They also say ChatGPT supports OAuth for MCP servers, and that it does not present custom API keys (OpenAI auth docs). That fits the Blueticks connector, which uses OAuth. OpenAI says ChatGPT currently requires manual confirmation before write actions. Plan rules are in connect WhatsApp to ChatGPT with MCP.
Lovable
REST route. Lovable's docs say secrets are stored in the app's built-in backend, and are "encrypted, injected into your Edge Functions automatically, and never reach the browser" (Secrets). They also warn that anything prefixed with VITE_ is a build-time value exposed to the browser. So the Blueticks key goes in Secrets, and an edge function makes the call, as in the recipe above. Lovable also documents custom connectors with a bearer-token method, where the credential is injected server-side. Creating one is on all plans and needs a workspace admin or owner (custom connectors).
MCP route. Lovable supports custom MCP servers on all plans, with OAuth, a bearer token or API key, or no authentication. The catch is stated plainly: chat connections "only give Lovable context in the project chat and in Chats" (custom MCP). Your published app cannot use it. Connect Blueticks over MCP to let Lovable's chat read your WhatsApp while you build, and use REST for the app.
Bolt
REST route. Bolt's server functions use secrets "to connect to outside services on your behalf", and the docs say never to paste secret values into project code (Secrets). They separate this from environment variables, which can be read by code running in the user's browser. Put the key in Secrets, call Blueticks from a server function.
MCP route. Bolt can connect an MCP server so the agent can read external tools and data, with API key, OAuth or no authentication (MCP). The page describes it as context for the agent. Use by a generated app is not documented, so I would not count on it. The docs also say connectors can slow Bolt down and raise token use.
Replit
REST route. Replit encrypts a secret and exposes it to your project as an environment variable, and says not to store API keys as plain configurations. Secrets are available for every deployment type except Static Deployments (Secrets). So you need a server component, and the key is read with process.env (or your language's equivalent).
MCP route. Replit Agent can connect to external tools through MCP, with OAuth or custom headers (connect via MCP). It is described as something the Agent uses. Whether a deployed app can use it is not documented. Use REST for the app.
Base44
REST route. This is the clearest of the group. Base44 backend functions can "connect to third-party APIs with protected credentials", and the docs show a fetch that sends an Authorization: Bearer header built from apiKey, where the key comes from secrets.get("API_KEY") (backend functions). Secrets live in the dashboard, and the docs say the full values never reach the browser (app secrets). That is the recipe above, almost word for word.
MCP route. Custom MCP servers need a Builder plan or higher, and they work "only in the editor chat while you build". Base44 says they cannot be called from app flows, workflows or backend functions at runtime (custom MCP). For a shipped app, REST is the only route.
Bubble
Bubble has a built-in API Connector, so no plugin is needed. Set authentication to "Private key in header", add a POST call to the send endpoint, initialize it, and use it as an action in a workflow. One warning: initializing makes a real request, so it sends a real message. Aim it at your own number. The full walkthrough is in Bubble WhatsApp integration with the API Connector.
FlutterFlow
REST route. FlutterFlow's API Calls let you set an Authorization header such as Authorization: Bearer YOUR_TOKEN. The docs add that making a call private "is helpful if it uses tokens or secrets you don't want to expose in your app", and that a private call is routed through Firebase Cloud Functions, which requires Firebase to be connected to the project (API Calls). So for the Blueticks key, mark the call private. A non-private call ships the token inside the app.
MCP route. I did not find custom MCP support for apps in FlutterFlow's docs. Use REST.
Glide
REST route. Glide Classic has a Call API action that lets you set an Authorization header, and it marks custom values as secret. The page says Call API is available for Business and Enterprise plans (Call API). The page does not say how secret values are kept from the browser, and it is labeled as Glide Classic. I did not find a custom REST call in the current GlideOS docs. Check which product your app is on before you start.
MCP route. Glide's MCP server runs the other way: it lets a client like Claude or Cursor connect to your Glide app (Glide MCP). I found no way to add an outside MCP server to a Glide app.
Softr
REST route. Softr's REST API data source supports a Bearer token, but it is read-only. Sending needs the Call API action (Professional plan and above) or a workflow (REST API data source, Call API). Neither page says whether the header value is hidden from the browser, so I cannot tell you it is safe there. For a custom code step in workflows, Softr says not to put API keys in the code and to attach the service as an integration (Run Custom Code). If you cannot confirm where your call runs, put a small server of your own in front.
MCP route. Softr's MCP server lets assistants like Claude and ChatGPT use your Softr workspace (Softr MCP). That is the reverse direction. I found no way to add an outside MCP server to Softr.
Which route should you pick?
| Builder | Safest place for the key | Custom MCP |
|---|---|---|
| ChatGPT-built app | Your host's server-side secrets | ChatGPT itself: yes, OAuth |
| Lovable | Secrets, read by an edge function | Chat only, all plans |
| Bolt | Secrets, read by a server function | Agent context; app use not documented |
| Replit | Secrets (not Static Deployments) | Agent; app use not documented |
| Base44 | Secrets, read by a backend function | Editor chat only, Builder plan+ |
| Bubble | API Connector private key in header | Not covered here |
| FlutterFlow | A private API call via Cloud Functions | Not found |
| Glide | Call API secret values (Business+, Classic) | Reverse direction only |
| Softr | Call API (Professional+); browser exposure not documented | Reverse direction only |
Pick REST for anything the finished app does on its own. Pick MCP for a person talking to an AI about their own chats.
What goes wrong most often?
- Nothing sends. Call
GET /v1/pingfirst and check thatwhatsappConnectionsis not empty. - A 401. The header is missing
Beareror the key is wrong. - A 403. The key lacks a scope. Use Full access.
- A 429. You hit a rate limit. Wait for
Retry-After. - A model invents an endpoint. Hand it the real ones. The group API guide and the REST API guide list them with curl and Python examples.
FAQ
Is this the official WhatsApp Business API? No. It sends through your own WhatsApp number via a connected Blueticks engine, so there is no Meta business verification or template approval.
Do I need a Blueticks plugin in any of these tools? No. Every route above is either the plain REST API or the hosted MCP connector.
Can an app builder's AI send WhatsApp messages for me while I build? Where the builder supports custom MCP, yes, in its own chat. Lovable and Base44 say it is chat-only, and for the others the docs describe agent context. A shipped app should call the REST API.
Want more WhatsApp recipes? Join the free WhatsApp Growth Recipes community.


