# SDK & API wishlist: what would help you build better experiences? **URL:** \ **Category:** API & SDK\ **Created:** [June 22, 2026, 6:20am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128 "2026-06-22T06:20:46Z")\ **Posts on this page:** 7\ **Page:** 2
**Author:** ![Cody](https://sea2.discourse-cdn.com/flex002/user_avatar/community.servicem8.com/cody/32/52_2.png) [@Cody](https://community.servicem8.com/u/Cody)\ **Post date:** [July 18, 2026, 5:20am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/21 "2026-07-18T05:20:19Z")
Hi Chad, Got it. We’ll add your +1 for `jobmaterial`, `companycontact`, `asset`, and `joballocation` object webhooks, plus the request that creation-time field values don’t also trigger change-style webhook handling, to the SDK/API wishlist. On the reliability side, the current webhook docs say 4xx/5xx delivery errors are retried for up to 72 hours before the webhook is automatically cancelled, and the API reference notes that repeated failed deliveries, including timeouts, can make a subscription inactive automatically. For debugging this today, `GET /webhook_subscriptions` supports `status=inactive` or `status=all`, and inactive subscriptions can include `last_failure_reason` and `last_failure_at` to help identify the last recorded failure. We’ll also capture the broader reliability-layer feedback, including clearer visibility when a subscription is deactivated and better handling around duplicate deliveries or re-deliveries. Thanks, Cody ---
**Author:** ![Tait\_from\_Tasklab](https://avatars.discourse-cdn.com/v4/letter/t/ad7895/32.png) [@Tait\_from\_Tasklab](https://community.servicem8.com/u/Tait_from_Tasklab)\ **Post date:** [July 25, 2026, 3:34am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/22 "2026-07-25T03:34:40Z")
It would be great if services were exposed to the api, so that they can be associated to a job when the job is created (via api) ---
**Author:** ![developer\_account](https://avatars.discourse-cdn.com/v4/letter/d/898d66/32.png) [@developer\_account](https://community.servicem8.com/u/developer_account)\ **Post date:** [July 25, 2026, 10:22pm UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/23 "2026-07-25T22:22:30Z")
**What:** Forms and Templates - it would be good if we could properly push both forms and document templates programatically via the API **Why:** while there is some support for both forms and templates, the current API does not allow us to properly push/update and link forms with their corresponding docx templates. This means there is a final step required to do it via the ServiceM8 UI. **How:** this will help to install and maintain custom forms and templates (inc quotes and invoices) for clients where we have them directly into their ServiceM8 systems via API key or OAuth. ---
**Author:** ![tom\_campbell](https://avatars.discourse-cdn.com/v4/letter/t/8baadc/32.png) [@tom\_campbell](https://community.servicem8.com/u/tom_campbell)\ **Post date:** [July 27, 2026, 2:47am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/24 "2026-07-27T02:47:30Z")
Supporting the `x-impersonate-uuid` header when using an API key would be very helpful for synchronising messages and notes between systems using a private integration. Without this, any messages coming from the external application will appear as if they’re from the API key user. ---
**Author:** ![jason\_gebert](https://avatars.discourse-cdn.com/v4/letter/j/b782af/32.png) [@jason\_gebert](https://community.servicem8.com/u/jason_gebert)\ **Post date:** [August 5, 2026, 7:40am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/25 "2026-08-05T07:40:19Z")
Notifications What - Notification access for us to display. Why / How - We run two way direct sms for booking with our ai agent and it would be handy for it to show up in notifications like 2 way sm8 sms works. ---
**Author:** ![marc\_walker](https://avatars.discourse-cdn.com/v4/letter/m/d2c977/32.png) [@marc\_walker](https://community.servicem8.com/u/marc_walker)\ **Post date:** [August 5, 2026, 8:23am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/26 "2026-08-05T08:23:01Z")
We’re using the ServiceM8 MCP connector with Claude to create jobs automatically from our recurring client schedule as service m8 recurring feature is to limited It’s working well, but there’s one real gap - create\_job only takes company name, address, description, and template, so there’s no way to add materials or pricing to a job through it. What’s interesting is this isn’t actually a limitation of the API itself - we can already read full job material data via jobmaterial.json, we use it for cost reporting today. The connector just doesn’t expose a way to write to that same endpoint. In practice this means we can copy a job’s description automatically when creating a new one, but then have to manually re-enter every line item and price afterward - which cancels out most of the time we’re trying to save. Would love to see something like add\_job\_material added so we can copy a previous job’s full details, including pricing, in one step rather than a separate manual billing pass every time. Guessing this would help anyone else building on the connector who needs to create genuinely complete jobs, not just bare-bones ones. ---
**Author:** ![anthony\_tassone](https://avatars.discourse-cdn.com/v4/letter/a/5e9695/32.png) [@anthony\_tassone](https://community.servicem8.com/u/anthony_tassone)\ **Post date:** [September 25, 2026, 11:03am UTC](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128/27 "2026-09-25T11:03:38Z")
Hi Cody, Adding to the list — I’m using the ServiceM8 connector with Claude AI to help manage jobs. Works well for creating jobs, adding notes, changing status and queues, and scheduling. A few things it can’t do yet that I can do manually in ServiceM8: · Set or edit job contacts (Job/Billing/Property Manager) · Set or edit badges · Set or edit PO number · Remove or cancel a job once it’s on the schedule (can add a booking, but no way to take it off) Would be great to see these added if there’s a plan to. Regards, Anthony [Previous page](https://community.servicem8.com/t/sdk-api-wishlist-what-would-help-you-build-better-experiences/1128.md?page=1)