Deal Creation Webhook signature not matching with monitoring tab

Developer Support APIs & Integrations
,
1

I have set up a Deal creation webhook. However, I am running into some strange errors. If I go to the webhook subscription details - then there is a test sample payload using which I can test. This is consistent with the webhook API doc.

[
{
“eventId”: “100”,
“subscriptionId”: 1576318,
“portalId”: 21920068,
“occurredAt”: 1651922693081,
“subscriptionType”: “deal.creation”,
“attemptNumber”: 0,
“objectId”: 123,
“changeSource”: “CRM”,
“changeFlag”: “NEW”
}
]

I can get the test to work with this. However, when I test my webhooks, they fail with 400 - and their signature is an object, not an array. Here’s an example (its all from the test environment)

{
“eventId”: 3569161897,
“subscriptionId”: 1576318,
“portalId”: 21924538,
“appId”: 862032,
“occurredAt”: 1651917294933,
“subscriptionType”: “deal.creation”,
“attemptNumber”: 7,
“objectId”: 8835693411,
“changeFlag”: “NEW”,
“changeSource”: “CONTACTS”
}

Can anyone confirm which version is correct? I am doing a rather simple test with Power Automate and cannot seem to get it to work which is rather frustrating. Many thanks for any pointers.

2

Hey, @SayanGhosh :waving_hand:

To confirm, an array is the expected result here – it is possible to have multiple hook objects being delivered.

@RMones and @rbthomas do you have any additional insight here?

Thank you! – Jaycee

3

Thanks @Jaycee_Lewis - that is helpful. The test webhooks are immediately firing 400 without reaching my server. Is there a way to use this test harness to use the right payload (postman works)? Can I just edit the payload to be an array on the textbox in the portal (would have to check if it’s editable) and try?

4

Seems like the webhooks test harness is now fixed, thanks!