> ## Documentation Index
> Fetch the complete documentation index at: https://moengage.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure Vonage
# Introduction
Vonage is a communication platform as a service (CPaaS) provider for consumers and businesses that makes it possible for customers to connect and communicate on any device through cloud-hosted voice, video, chat, and short message service (SMS). For the latest details on Vonage's SMS capabilities and API setup, refer to Vonage's [SMS Channel User Guide](https://api.support.vonage.com/hc/en-us/articles/29661933371036-MoEngage-Connector-SMS-Channel-Guide).
**Prerequisites**
Ensure you have access to your Vonage dashboard.
# Configure Vonage as a Custom SMS Connector (Service Provider)
The Vonage Conversations for MoEngage connector runs on Vonage Cloud Runtime. Setup involves creating a custom SMS sender in MoEngage, deploying the connector instance, generating a bearer token in the connector admin panel, and completing delivery tracking. The connector supports two operating modes: Standalone and Conversational Connect.
For prerequisites, step-by-step configuration, delivery field mappings, and troubleshooting, refer to the [Vonage MoEngage Connector SMS Channel Guide](https://api.support.vonage.com/hc/en-us/articles/29661933371036-MoEngage-Connector-SMS-Channel-Guide).
# Alternative: Direct Vonage SMS API (Without the Connector)
This article will help you set up Vonage as a custom service provider on the MoEngage dashboard.
Before proceeding, ensure you have the following parameters for calls to Vonage API (Nexmo). You can find your **Key** and **Secret** in [Vonage Dashboard](https://dashboard.nexmo.com/private/dashboard). You can also [read about Vonage SMS API here](https://docs.nexmo.com/messaging/sms-api/api-reference#authentic).
| Parameter | Description |
| - | - |
| api\_key | - Your Key. For example: `api_key=n3xm0rocks` |
| api\_secret | - Your Secret. For example: `api_secret=12ab34cd` |
Log in to the MoEngage Dashboard and follow these steps:
1. Navigate to **Settings** > **Channels** > **SMS & RCS** > **Sender configuration** > **SMS**.
2. Click **+Add SMS Sender** at the top right corner.
3. Add the following details in the **Sender Details** screen.
| Field | Description |
| - | - |
| **Mark as default** | Turn on this toggle to mark the sender as the default sender for the service provider being configured. If marked as default, this sender would be used for sending all SMS campaigns from MoEngage unless you select a different sender while creating the campaign. |
| **Service provider name** | This field identifies the service provider you are configuring on the MoEngage Dashboard and has to be unique. Type the name of the service provider here. |
| **Sender name** | This field identifies the readable sender name that can be used while creating a campaign or alert. |
| **Sender type** | The Sender type can either be **Promotional** or **Transactional**. Choose the Sender type as Promotional when you would be using the Sender for sending information about your brand, promoting deals, or engaging with users. Choose the Sender type as Transactional when you would be using the Sender for sending alerts about transactions, OTPs, security information, or any information that can be classified as transactional in nature. |
4. Configure the Webhook by adding the following details:
| Field | Description |
| - | - |
| **API URL** | This field contains information about the URL that should be used to send an API request to the Sender. You can get this information from the API Documentation of the Sender. Type the API Endpoint of the sender here. The Vonage URL is: [https://rest.nexmo.com/sms/json](https://rest.nexmo.com/sms/json) |
| **Method** | Select **POST** as the HTTP method. |
| **URL Parameters** | Add the URL Parameters to be passed to the API as Key-Value pairs using this option. You can get this information from the API Documentation of the Sender. For example, if the API URL call uses the GET method, all the parameters, such as API Key, Authorization, and so on, are passed as URL Parameters. |
| **Headers** | Add the Request Headers to be passed to the API as Key-Value pairs using this option. You can get this information from the API Documentation of the Sender. Add the Authorization Header. |
| **Body Type** | Choose the Body Type as **Form** and add the following details:
1. You can find your **Key** and **Secret** in [Vonage Dashboard](https://dashboard.nexmo.com/private/dashboard).
2. In the **to** field, add *Moesms\_destination* to pass the mobile number of the user.
3. In the **text** field, add *Moesms\_message.*
4. In the **from** field, add the sender ID of your account provided by Vonage. |
5. **Send a test SMS** to verify your configuration.
6. Click **Save** to save the Sender Configuration.
7. You can configure delivery tracking after creating the sender in the MoEngage Dashboard. For information about Delivery Tracking, refer to [Delivery Tracking for Custom Connectors](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/getting-started-with-sms/configure-an-sms-sender).
# Next Steps
* Create an SMS campaign using the [Getting Started for creating SMS campaign](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/create-an-sms-campaign).
* Set the [Frequency Capping for SMS](/docs/user-guide/settings/channels/delivery-controls/frequency-capping).
* Set the [Current Service Provider](/docs/user-guide/campaigns-and-channels/sms-mms-and-rcs/sms/getting-started-with-sms/configure-an-sms-sender).
* [Read more about campaign analytics.](/docs/user-guide/campaigns-and-channels/connectors/analyze/connector-campaign-analytics)
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.