Discussions

Currently, the new Events Webhooks in ServiceM8 still have a few major issues that make them difficult (or in some cases impossible) to use in production.

OAuth 2.0 Support

• With OAuth 2.0, you can successfully register multiple different webhook subscription events (from the list of ~25).
• You can also retrieve the list of subscriptions (GET /subscriptions) and see them as an array.
• Deleting subscriptions also works as expected.
• So, on paper, OAuth 2.0 seems fine.

Badge Event Glitch

• I’ve identified a glitch specifically with badge add/remove events.
• If you add one or more badges and then close the job card → webhook fires correctly.
• If you remove one or more badges and then close the job card → webhook fires correctly.
• BUT if you remove and then add (or vice versa) in the same session before closing the job card, no webhook is sent at all.
• My use case requires swapping badges in one session, so this makes the event unusable.

API Key Problems

• Using an API key instead of OAuth:
  • I was able to receive webhook payloads (e.g., job status changes), which was promising.
  • However, subscribing (POST /subscriptions) and deleting (DELETE /subscriptions) did not work — no array of webhooks, no ability to manage them.
  • The endpoint responded with “success,” but nothing actually happened.

Summary

• OAuth 2.0 works (with the badge glitch), but API keys don’t let you manage event subscriptions.
• Badge add/remove swap events are broken and don’t fire.
• This is pretty frustrating because I’ve tested this thoroughly and need these events to be reliable.

👉 Can ServiceM8 please confirm what’s going on here, and whether these bugs are on the roadmap to be fixed? Right now, events webhooks are not production-ready.