Taddy API is constantly being updated with the latest podcasts and episodes. If you use our webhooks feature, instead of you having to manually check Taddy API for new podcasts or episodes, we send you the details on new podcasts and episodes to an endpoint on your server.

Moreover, you have the ability to add webhook filters, so instead of getting a webhook event for every new podcast or episode, you can use filters to add a regex expression and only get notified for the specific content you care about.

Use-cases for Webhooks

• Do you want to monitor your brand? Set up a filter to get notified whenever your brand or website are mentioned.
• Are you doing sales intelligence or lead nurturing? Set up a filter to get notified when a potential lead appears on an episode, get the transcript of the episode and use this data for insights or lead scoring.
• Are you doing competitor or industry research? Set up a filter to get notified when an industry keyword or competitor’s key executive is mentioned, get the transcript of the episode and use this data for insights.
• Are you building a podcast player and want to send push notifications for new episodes? Set up a webhook without any filters to get notified whenever a new episode is released, then on your server, match against your users' subscriptions and send them a push notification.

Setting Up a Webhook

• Open up the Taddy Dashboard, you will see a “Setup a New Webhook” button.

Then, make sure you:

1. Enter in the endpoint where you want to receive the notifications (usually on your own server, but you can also point this to a Zapier, n8n, Make or Gumloop workflow)
2. Select which webhook events you would like to receive.
3. Optionally, you can add one or more webhook filters.

Note:

• You must be on the Business plan to add a webhook to your account.
• Receiving a webhook event does not count against your monthly API limits 🥳.
• You can use webhook.site to easily check what a webhook event sent from Taddy API looks like. Just paste in the unique URL from the website as your webhook endpoint to start receiving webhook events.
• Alternatively, here is some example code to set up your webhook endpoint.
• The endpoint url you enter into the Taddy API Dashboard needs to be one publicly accessible over the internet. (For example, 127.0.0.1 and localhost URLs will not work, since Taddy servers will not be able to contact your local computer). If you’d like to test receiving these notifications locally on your computer, Ngrok provides a useful & free way to do so. (It provides you a public url that is mapped to your localhost).
• Your endpoint url needs to be a POST endpoint
• On the Taddy API Dashboard, after you set up a webhook we will display your webhook’s secret. This is an optional but recommended security feature. We include this secret in the X-TADDY-WEBHOOK-SECRET header with every webhook event sent to your endpoint. Keep this secret confidential, your endpoint URL may be publicly accessible, but by verifying that the X-TADDY-WEBHOOK-SECRET header matches your secret you can be confident that any data you receive on your endpoint is from us and can be trusted.
• By default, every business account has access to one webhook endpoint. Reach out to [email protected] if would like to increase your limits.