# Configuring SMPP Connection

Mobivate BulkSMS supports SMPP connections for high-throughput and low-latency message delivery. SMPP access is authenticated using your existing API key.

### Authentication

To connect to Mobivate BulkSMS over SMPP, you will need a **valid API key**.

Your API key is split into two parts and used as the SMPP credentials:

* The **first half** of the API key becomes your `system_id`
* The **second half** of the API key becomes your `password`

#### Example

If your API key looks like this:

```
v-1234-56789-acde-fffff:aaaaa-bbbbb-ccccc-ddddd-eeee
```

Your SMPP credentials would be:

| SMPP Field | Value                        |
| ---------- | ---------------------------- |
| system\_id | v-1234-56789-acde-fffff      |
| password   | aaaaa-bbbbb-ccccc-ddddd-eeee |

### Required Permissions

Your API key **must** have the following permission enabled:

```
create:SingleSMS
```

Without this permission, SMPP message submission will be rejected.

### SMPP Connection Details

Use the following connection settings when configuring your SMPP client:

| Setting  | Value       |
| -------- | ----------- |
| Hostname | \<hostname> |
| Port     | 2775        |

{% hint style="info" %}
The hostname shown in this documentation use a **sample hostname**. The production SMPP hostname is provided by our team upon request.
{% endhint %}

### Security Recommendations

We strongly recommend **restricting API key access by whitelisting IP ranges** to prevent unauthorized use.

IP restrictions can be configured when managing your API keys in the Mobivate dashboard.

{% hint style="warning" %}
Treat your SMPP credentials with the same care as your API keys. Do not expose credentials in client-side code or public repositories.
{% endhint %}