What's New in PipesBot: a Daily Send Limit on Pool Numbers, a Webhooks Tab and 7-Day Retention
Short version: every sandbox (Pool) number you activate can now send 5 messages per UTC day. Receiving is still unlimited, the limit is the same on every plan, and BYON numbers have no daily limit. When you hit it, the API answers 429 DAILY_LIMIT_REACHED with the time it resets. This week we also shipped a Webhooks tab on every App, with a delivery log and manual retry, and we now delete stored webhook payloads after 7 days.
Pool numbers: 5 sends per day
Why
When we launched sandbox (Pool) numbers, we left them wide open on purpose, so anyone could plug in an agent and see WhatsApp come alive in minutes. You used them far more than we imagined.
Then on October 1, Meta started charging for service messages: every reply sent inside the 24-hour window. Sandbox numbers belong to PipesBot, so each of those replies lands on our bill, and at the volume the sandbox reached we can’t keep it unlimited. The sandbox goes back to what it was built for: trying PipesBot, testing, and light personal use.
Exactly what the limit is
- 5 sends per UTC day, per Pool number you activated. The count resets at 00:00 UTC (21:00 in Brasília).
- Same on every plan. Upgrading doesn’t raise it.
- Receiving is unlimited. Inbound messages keep arriving at your agent as before.
- Only sends Meta accepts count. A request rejected before it reaches Meta (validation, the 24-hour window, template errors, the 60-per-minute rate limit) doesn’t use your quota. If Meta fails the send, the slot is given back.
- System messages don’t count against you. The welcome message for unknown contacts goes out at most once per sender per number every 24 hours, and the “agent offline” notice now goes out once per day per number instead of every hour.
- BYON numbers are not affected. PipesBot puts no daily limit on them.
The limit applies to every way you can send from a Pool number: POST /v1/messages/send (text and media), POST /v1/messages/passthrough with a pk_ key, and WebSocket replies (whatsapp_reply), which is how the agent plugins answer.
What your code sees
Sandbox sends now carry X-Daily-Limit, X-Daily-Remaining and X-Daily-Reset headers so you can track the quota: X-Daily-Limit is always 5 and X-Daily-Remaining tells you how many sends that number has left today.
The sixth send of the day returns 429 with code DAILY_LIMIT_REACHED and a Retry-After header with the seconds left until 00:00 UTC. Over WebSocket, the reply_status event comes back with success: false and code: "DAILY_LIMIT_REACHED".
If your agent replies from a Pool number, handle this code the same way you handle rate limits: stop sending, tell the user if it makes sense, and try again after Retry-After. Don’t retry in a loop, since every attempt will get the same answer until the reset.
How to go past it
If your agent outgrew the sandbox, connect your own number with BYON. Your WhatsApp Business Account pays Meta directly, and PipesBot puts no daily limit on it. It takes about five minutes with Embedded Signup, and registration is now automatic. If you’re unsure which fits, Pool vs BYON walks through the trade-offs.
The details are in the sandbox docs.
A Webhooks tab on every App
Each App now has a Webhooks tab that lists the last 7 days of deliveries to your endpoint:
- filters for All / Failed / Delivered and by event type (
messages, v2 fields,number.onboarded,template_status_update,test); - a detail view with status code, duration and attempts, and the payload for failures;
- Retry for one delivery, or Retry all failed, which replays them oldest first to your current webhook URL.
A failed delivery is recorded after 3 attempts. If your endpoint was down for an hour, you can fix it and replay what you missed instead of losing those events. Template status updates, which used to be dropped after 3 failures, now go through the same path and can be retried too.
Webhook payloads are deleted after 7 days
When a delivery fails, we keep its payload so you can retry it. That payload can contain end-user message content, so it now has a retention limit: every stored delivery is removed from our live database once it is 7 days old, whatever its status, by a recurring cleanup job, and a payload is removed as soon as a retry succeeds. Copies in database backups are overwritten in the normal backup cycle. Successful deliveries are logged without their payload.
Along the same lines, we tightened our server logs so database errors are recorded by name and code only. Those error messages can echo the values in a query, and we don’t want any of that in logs.
A new look for the dashboard
The app at app.pipes.bot now uses the PipesBot design: new type and colors, a dark mode that follows your OS (with a toggle in the top bar), a mobile menu, and refreshed emails. We also removed the search box and notifications bell from the dashboard header, since neither did anything yet.
Try it
Everything above is live now. Open the dashboard to see your App’s Webhooks tab, and if your agent needs more than 5 sends a day, connect your own number with BYON.