Loading…
Loading…
Authenticate with an API key. UlaloBots stores only a hash of the key. Each outbound webhook has its own signing secret. This sends and reads WhatsApp. It does not drop every chat into a CRM for you.
POST /messages/send to: 265991234567 body: Your order is on the way.
Calls use x-api-key. UlaloBots stores a hash of the key, not the key itself. Launch and Scale both include keys. Lead with the inbox and replies, then connect software when you need it.
Only the hash is stored
Send text, image, video, audio, a document, or an approved WhatsApp message. List guided chats, approved messages, and conversations.
Same number as the inbox
Each webhook endpoint has its own signing secret. Events include message received, message sent, status updated, and automation executed.
HTTPS, with that secret
You can start a guided chat from a website, app, or back office. What a CRM does with those events is your build, or a custom Provider engagement.
Not a CRM push
No. UlaloBots can send and read WhatsApp, and it can POST signed events to an HTTPS address you control. A CRM mapping is something you build, or you talk to us about a Provider engagement.
Meta delivers WhatsApp events into UlaloBots. Separately, you can subscribe your own HTTPS endpoint to signed events from UlaloBots.
Live plan cards include API keys on Launch as well as Scale. Use them when your software must send or read. The shared inbox and the first reply still come first.
Connect a WhatsApp business number, set the first reply, and answer as a team with the full history.