Hubspot signature validation failing, earlier working properly for v1, is there any update done on version v1 signature?
Hi @ShobhaPatwal and welcome, we are so glad to have you here! 
Thanks for reaching out to the HubSpot Community!
I see that you posted on an older thread here: “X-HubSpot-Signature validation fails for custom workflow action’s request”, so I moved your post for more visibility.
For information, here are some resources on the topic that might help you:
- Validating requests from HubSpot
- Introducing version 3 of Webhook signatures
And this older thread “X-HubSpot-Signature for CRM Extensions” might point you in the right direction.
Could you please share additional details, like the method used, the body of the request and the result of the request?
The more info, screenshots (without sensitive/confidential information), and details you can provide, the better the Community can assist.
I’d love to check with our Top Experts: Hi @sylvain_tirreau, @Anton and @zach_threadint do you have any tips to help @ShobhaPatwal, please?
Have a lovely day and thanks so much in advance for your help! 
Bérangère, Community Manager
I am using the POST method for hubspot custom workflow action, where I am calling the endpoint of my app and verifying the hubspot signature.
Body returing to my endpoint is as follow:
{
"origin": {
"portalId": PORTAL ID,
"userId": null,
"actionDefinitionId": 220723090,
"actionDefinitionVersion": 1,
"actionExecutionIndexIdentifier": null,
"extensionDefinitionId": 220723090,
"extensionDefinitionVersionId": 1
},
"inputFieldName": "gateways",
"fetchOptions": {
"q": ""
},
"objectTypeId": "0-3",
"fields": {},
"objectTypeIdsForObjectCoordinateFields": {},
"userId": 23647734,
"inputFields": {},
"extensionsDefinitionVersion": 1,
"portalId": Portal ID,
"extensionDefinitionId": 220723090
}
Unless I’m mistaken, it seems to me that Hubspot is now sending requests in v2 because Custom Workflow Actions are treated as extensions.