Job Site Webhook - Test Output Doesn't Match Actual Output

[JenniferM]

I have set up a webhook subscription for when a Job Site is updated or deleted. I have discovered the output I get when I test the subscription (via the link on the subscription setup page) doesn't match the actual output I get when the webhook is triggered by an update/deletion.

Job Site Test Triggered Output:
ID: test.updated
build: xxxxxx.simprosuite.com
description: Test #1 has been updated.
name: Test
action: updated
reference testID: 1
date_triggered: 2025-04-10T15:08:32-05:00


Job Site Actual Triggered Output:
id: site.updated
build: xxxxxx.simprosuite.com
description: Site #1412 has been updated.
name: Site
action: updated
reference company_id: 0
date_triggered: 2025-04-11T08:58:16-05:00

In particular, the test output includes the job site ID (testID:1) as a reference property. However, the actual output only includes the company_ID property. While the job site ID does appear in the description, that is MUCH harder to pull out than if it is an actual property. Personally, I don't need the company ID as we only have a single company. However, I think the proper output should be like what you see for a customer webhook, which includes both the company_id and the customer_id. Having both properties allows you to build the proper API call to retrieve details for the record.

Customer Actual Triggered Output:
id: company.customer.updated
build: xxxxxx.simprosuite.com
description: Company customer #33 has been updated.
name: Company customer
action: updated
reference company_id: 0 customer_id: 33
date_triggered: 2025-04-10T10:26:55-05:00

[SimproAPITeam]

Hi JenniferM,
Thank you for your input and suggestions.

We understand what you mean and how the data would be easier to use on your end when it's assigned a property.

We will take this into account for future updates to our webhook data and see if we can add new properties in addition to the existing ones without breaking anything for current users.

Regards

[JenniferM]

I appreciate the feedback. Honestly, it seems like an error/oversight as it doesn't match the webhooks for other tables (e.g. customers, contacts). As it currently exists, it's actually pretty useless.

In addition, at a minimum you need to make the test subscription (from within the webhook subscription setup) match what actually happens. As mentioned in my original post, the test output doesn't match the actual output, making it very confusing.

[SimproAPITeam]

Hi JenniferM,

Thank you for bringing this to our attention. You've made a fair point.

We've raised it internally for improvements we can make to improve the experience.