Notification webhooks vs. General webhooks (Notification webhooks not working)

I’m trying to use the notification service for a webhook to trigger a lambda in aws. Everything is set correctly, but it’s not working - the function is not called.

When I tried setting the webhook from ‘general’, it worked, but I want to do it only for one category (transactions) and this is why I wanted to use the notification webhooks.

Can you please explain if I misunderstood in the purpose of the notification webhooks, and is there anything else that needs to be done to make them trigger a function like the general webhooks?

Hey @stavbarak,

Thanks for reaching out!
Let me shed some light on that:

  1. Notification center is used for Audit Log information. You can get these audit logs either via slack, email or a webhook notification. These events are dedicated only for audit log purposes and contain limited information about transactions.

  2. Webhooks (under the General setting) is the developer webhook we provide our clients with. It fires a POST call to your endpoint upon every event created in your workspace. The list of events can be found here.

If you are looking to get an extensive information about transactions in your workspace and create event driven architecture you should go with #2. There is also a difference in the authentication mechanisms between the two so I assume that your lambda is configured with the authentication mechanism for the developer webhook and not the audit log one.

Currently, we do not support subscription to specific events in the developer webhook feature (working on it and it’s planned for later this year) so you will need to filter the incoming notifications on your end.

Hopefully it makes a bit more sense now.

Thank you for the explanation. For my use case I want to send the notification to an endpoint on AWS lambda. I only need the limited payload that comes from the audit. Is that not possible as is? Or are you suggesting I use the Webhooks under the general setting and filter out manually?

Hey Stav,

Both are fine and should work. It all depends on the data you need. If you need a detailed data about the transaction including transaction fees, sub-status, block height and number and more you should use the developer webhook (under General settings) while filtering on your side the relevant events.

If you just need to be aware of the fact that there was a transaction and the data is not important, you can use the Audit Log notification (under Notifications Center) and consume transaction events only.

Kindly note - as mentioned previously, the authentication method of both is different.
While the developer webhook is sent with the Fireblocks-Signature header that contains the signed payload with Fireblocks private key (you should verify the signature with the public you get from the documentation), the audit log webhook is signed with a symmetric key provided by you while configuring it via the WEB console.

Thank you very much @SlavaSereb