WABA logs
Search and audit outbound WABA sends.
Open Channel → WABA → Logs.
What this page is for
Paginated outbound send history for WABA (WhatsApp Cloud API) only: log ID, device, recipient phone, message preview, delivery status, and timestamp.
This is the same data as Logs → History, filtered to the WABA channel. Use it when you need to trace a specific Cloud API send without mixing in Fonnte WhatsApp, Telegram, or email rows.
Sample data shown.
Search and filter
Search is field-based: click the search area first, pick which column to search, then type your query.
| Step | What happens |
|---|---|
| 1. Click search | A Search in popup opens — you must choose a field before typing |
| 2. Pick a field | Recipient, Log ID, or Message |
| 3. Type | Kirisan filters the table as you type (short debounce) |
After you pick a field, the search bar shows the field name on the left (for example Recipient ▼). Click it to switch fields — changing the field clears the query and reloads the list.
On the same row as search (to the right):
| Filter | What it does |
|---|---|
| Device | Limits rows to one connected Cloud API number — pick All devices or a specific WABA device |
| Status | All statuses, Sent, or Failed |
Device and Status apply together and also apply to Recipient / Message window search and Continue search steps.
Device filter
Open the Device dropdown to pick a WABA device. The list shows each connected number as display name · phone (same labels as on Devices).
When you have many devices, use the search box inside the dropdown — it matches the display name or phone number. All devices stays pinned at the top.
| Situation | What you see in Device column |
|---|---|
| Send logged after device tracking shipped | Display name + phone (or phone only if unnamed) |
| Older send before device was stored | — (empty) — use recipient, message, or date instead |
Search fields
| Search field | Matches | Minimum length |
|---|---|---|
| Recipient | Phone numbers that contain your query (for example 7890 matches 6281234567890) | 3 characters |
| Log ID | The full, exact numeric ID from the ID column — not a partial match (for example 48291, not 482) | Full ID only |
| Message | Message body text that contains your query (for example order anywhere in the text) | 3 characters |
Recipient and Message search scan the most recent 1,000 sends per step (respecting your Device and Status filters). When older sends remain, Kirisan shows Continue search — same behavior for both fields.
Log ID is different: enter the complete ID exactly as shown in the table. Kirisan does not match prefixes or fragments — 482 will not find row 48291.
If you type fewer than three characters for Recipient or Message, Kirisan waits until the minimum is met and shows a short hint under the search bar.
Window search and Continue search
Recipient and Message search do not scan your entire log at once. Each step reads the most recent 1,000 sends (respecting Device, Status, and the active search field), then looks for your query inside those rows — phone number substring or message text.
When Kirisan finishes a step and older sends still exist, a bar appears below the table with Continue search:
| Situation | What you see |
|---|---|
| Matches in this 1,000 | Matching rows in the table; bar explains how many were found and offers Continue search if more history remains |
| No matches, older rows exist | Empty table message for that batch; Continue search scans the next 1,000 |
| No matches, end of log | No ”…” found in your WABA log. — nothing left to scan |
Click Continue search as many times as you need. New matches from later steps are added to the table. You decide when to stop.
Log ID search uses an index and returns results immediately — it does not use Continue search.
Log table
Each row is one outbound WABA send:
| Column | Meaning |
|---|---|
| ID | Unique send row ID — copy the full number for Log ID search (exact match only) |
| Device | Which Cloud API number sent the message (display name + phone when configured on Devices) |
| Recipient | Destination WhatsApp phone number |
| Message | Truncated preview of the message body or template text |
| Status | sent (green) or failed (red) |
| Date | When the send was recorded |
Rows are clickable — Kirisan opens a WhatsApp-style preview of the full message.
Message preview
Click any row to open the preview popup:
Close the preview with the × button, by clicking outside the bubble, or with Escape.
Pagination
When you are not using Recipient or Message window search, pagination below the table appears for long lists (for example Showing 1–25 of 312 · Page 1 / 13 with Previous and Next).
During Recipient or Message search, results from each Continue search step accumulate in the table instead of using page numbers.
Tips
- Run two Cloud API numbers? Filter Device first, then search Recipient or Message — you only scan sends from that device.
- Start with Recipient when a customer asks “did you message my number?” — use at least three digits anywhere in the number.
- Use Log ID when you have the full send ID from the table, an API response, or support — partial IDs do not work.
- Use Message when you remember part of the template or body text but not the recipient — click Continue search to look further back in time.
- Filter Failed and pair with Device or Devices if failures cluster on one disconnected number.
- Cross-channel history lives under Logs → History — see Message logs.
Related
- Statistics — delivery rates and volume trends
- Message logs — History, per-channel logs, webhooks
- Devices — connection status when sends fail
- Templates — Meta-approved message layouts used in sends