When you build your application using Twilio API's, you may want to receive inbound HTTP(S) requests (also known as webhooks) from Twilio's servers. These webhooks contain information about events that have just occurred - for instance, a text message was sent to a Twilio phone number.
Some of these webhooks are informational (such as letting you know that a voice call recording is ready for download), and others require your web application to respond (for instance, letting Twilio know what to do when someone calls your Twilio phone number).
In all of these cases, you will need to tell Twilio what URL to send these webhooks to.
Ready to start building webhooks for Twilio in your own web application? Read this guide to get started with webhooks.
Each Twilio product uses webhooks differently. To learn more about which webhooks each product uses, and how to set them up with your application, visit these pages:
Webhooks aren’t just limited to products. You can also have Twilio send you webhooks when events occur in your application, such as billing levels reaching a certain threshold, or if an error occurs when Twilio calls your web application. You could setup a pipeline that sends your webhooks into Slack, Microsoft Teams, or another chat system. You could also set up a webhook that notifies you via email.
Learn more about each of these areas on these pages:
Get an in-depth discussion of webhooks, learn how to validate that inbound webhooks are from Twilio, and read answers to questions from the Twilio developer community.
Ready to start implementing webhooks with your own application? Want to see what capabilities webhooks have? Follow along with these tutorials to learn how to track delivery status for messages, reply to text messages, or to use Azure Functions to create serverless webhooks.
- SMS と MMS メッセージを受信し返信する
- Azure FunctionsとC#によるサーバーレスのWebhook
- Azure FunctionsとNode.jsによるサーバーレスのWebhook
- ASP.NET MVC Webhookプロジェクトの作成