Webhook issues

If Beds24’s webhook to PingTeo is failing or you see errors, use this guide.

401 Unauthorized

• Cause — PingTeo rejected the request because the secret (e.g. X-PingTeo-Auth header) is wrong or missing.
• Fix — In Beds24, set the exact secret value that PingTeo shows in Settings → Beds24 (or webhook setup). No extra spaces or different casing. If PingTeo doesn’t require a secret, remove it from Beds24.

404 Not found

• Cause — The URL path or user ID in the URL is wrong. The webhook URL should look like .../api/beds24/webhook/YOUR_USER_ID.
• Fix — Copy the full URL from PingTeo again and paste it into Beds24. Ensure the user ID segment is correct (no typo, no old ID).

500 or server error

• Cause — PingTeo or the server had an internal error processing the webhook (e.g. DB or downstream API issue).
• Fix — Retry later. If it persists, note the time and (if visible) request ID or error message and contact support. Beds24 may retry; check Beds24’s webhook logs for retry status.

Webhook not firing at all

• Cause — Beds24 isn’t sending (wrong URL, webhook disabled, or not configured for message/booking events).
• Fix — In Beds24, confirm the webhook is enabled, the URL is correct, and the events (e.g. new message, booking update) are selected. Use Beds24’s test/ping if available.

Ping / test succeeds but real events don’t

• Cause — Ping might hit a simple health endpoint; real payloads might use a different path or need specific headers/body.
• Fix — Ensure Beds24 is sending real message or booking payloads to the same URL. Check Beds24 docs for webhook payload format and that PingTeo supports it.

Next: Common errors — Other frequent issues.