You need to configure both your Inbound Message and Message Status webhooks.
There are at least two webhooks you must configure:
- Message Status webhook
- Inbound Message webhook
When messages status updates are generated, such as
accepted, callbacks will be received on the Message Status webhook URL.
When an inbound message is received, a callback with message payload is invoked on the Inbound Message webhook URL.
IMPORTANT: Both webhook URLs should be configured. At the very least your webhook handlers should return 200 responses for both Inbound Message and Message Status callbacks. This ensures potential callback queuing issues are avoided.
Click Edit to modify the application's webhook URLs.
In the Messages capabilities section, enter your webhook URLs in the fields labeled Status URL and Inbound URL.
The values you enter for webhook URLs depends on where your webhook server is located. For example:
NOTE: The default method of
POST should be used for both of the webhook URLs.
Messages API does not support inbound SMS message and SMS delivery receipt callbacks via the application-specific webhooks described in the previous section. In order to receive callbacks for SMS message and SMS delivery receipts you need to set the account-level webhooks for SMS.
If you want to test your application locally you can use Ngrok.
See our information on Using Ngrok for local development
If using Ngrok in this manner you would use the Ngrok URLs for your webhook URLs:
Please note that webhooks emanating from Nexmo, such as those on your Message Status webhook URL and Inbound Message URL, are queued by Nexmo on a per-message basis.
Please ensure that all applications acknowledge webhooks with a 200 response.
In order to validate the origin of your webhooks, you can validate the signature of the webhooks, see instructions here
If the Webhook URLs for messages in your Nexmo Account are already in production use and you would like a second one for using the Messages API, please email email@example.com and ask for a sub API Key.