Vendor-level webhooks receive notifications for all of your products, while product-level webhooks only receive notifications for the specific product it's configured for. Most of our customers choose to use vendor-level webhooks, but depending on your use case, a product-level one might be more useful. These can be configured when you Create or Update a Webhook.
We provide 2 options for configuring webhooks. With our product-level webhooks, you can configure each of your products with a unique webhook URL to receive event data for specific product. With our vendor-level webhooks, you can receive all event data for all of your products at a single webhook URL. Depending on your use case, it may make sense to have unique product-level webhooks configured or it may make sense to have one vendor-level webhook configured to capture events for all of your products.
Our egress IPs are the following:
Your Webhook endpoint must accept requests from these IP addresses.
API requests to your webhook endpoint will be
Tackle’s unique subscription event identifier, which provides a unique ID for any Marketplace subscription event, is currently limited to AWS only, but will be extended to Azure and GCP Marketplace orders soon.
There are a number of reasons Tackle might get a 500 error from your endpoint. We recommend using our Test a Webhook endpoint to help debug your issue. Calling this would send a test payload to your endpoint along with any error messages we might be seeing.
Note that some errors might be specific to an event type. Try to pass different event types to the Webhooks Testing endpoint to make sure you've covered the different edge cases.
Updated 3 months ago