Webhooks are not arriving
Warsita posts each event to the session's webhook URL and retries for about two and a half hours when your server does not answer. To find out what is wrong, start from the session's Webhook tab.
Check the setup
- The URL must be public and use
https. Addresses on a private network orlocalhostare refused. - The events you need must be ticked.
messages.receivedcovers every chat; the personal, group and channel variants are narrower. - Filters in session Settings: with Ignore groups, Ignore broadcasts or Ignore channels on, those chats' messages are not sent at all.
Send a test
Use the simulator on the Webhook tab to send a signed sample of any event. It shows the status code your server answered and how long it took.
Read the delivery log
The log on the Webhook tab shows the last deliveries with their result:
| You see | Likely cause |
|---|---|
401 or 403 |
Your server rejected the signature. Check you verify the raw body with the current secret; rotating the secret changes it at once. |
404 or 405 |
The path or method is wrong: Warsita sends POST to the exact URL. |
5xx |
Your server failed. Check its logs. |
| Timeout | Your server took longer than 10 seconds. Answer 2xx first, then do the work. |
Once your server is fixed, click Resend on failed deliveries to send them again. How to check signatures, with code, is in Webhooks.
Still stuck? Email hello@warsita.com with your workspace and session name.