Webhooks are a great introductory step towards automation as a creator and allow you to receive events from us on external platforms such as Discord, Slack, or your own web application. They can be created and managed by navigating to our creator dashboard page and all creators are allowed up to 20 active webhooks at any one time.
These are the events that will trigger your webhooks to be called. Each trigger supports a list of placeholders that you can place in your request body which will be replaced with event data. These placeholders may be updated on occasion so can be found on the webhook creation & editing pages. You can further specify filters on these triggers so that they will only be called for specific resources or categories.
Purchase - filter by all, resources or categories Review - filter by all, resources or categories Update - filter by all, resources or categories Publish - filter by all or categories
The only request method supported currently is POST. You may provide a custom content type but we currently only support placeholder encoding for application/json and application/x-www-form-urlencoded. If your content type is not one of these and requires values to be encoded, your request body may become invalid. Please open a support ticket to request support for additional content-type encodings. We provide templates for Discord and Slack to get you started with just a few clicks!
When receiving webhooks to your own web application, it's recommended to include a secret within the request body to verify that the requests you receive originate from BuiltByBit. These could be included within the actual URL, such as what Discord & Slack do with their webhooks URLs.
When we receive an error from your webhook, be that either a non-2xx response code or a timeout, we will schedule additional attempts to be made. Specifically, attempts will be scheduled for 15 minutes after the initial one, then 1 hour after that one, and then 6 hours after that one. If none of these attempts succeed, no further attempts will be made. We will additionally disable the webhook entirely if all four attempts fail for the webhook consistently without receiving a successful response. You may manually re-activate the webhook via the creator dashboard page once you're confident any issues have been resolved.