# HTTP IN trunk settings reference

This reference describes the fields available when creating or editing an
HTTP IN trunk. The settings are grouped by the form sections shown in the
DIDWW User Panel.

For configuration steps, see [Create an HTTP IN trunk](how-to-guides/create-http-in-trunk.html) or [Manage HTTP IN
trunks](how-to-guides/manage-http-in-trunk.html).

## General settings

The **General** section identifies the trunk and defines how incoming SMS
messages are delivered to your HTTP endpoint.

| Field | Availability | Description |
| --- | --- | --- |
| Friendly name | Required | Unique name used to identify the trunk. For example, `My HTTP IN Trunk`. |
| HTTP Method | Required | HTTP method used to deliver messages: `GET`, `POST`, or `PUT`. Default: `GET`. The [Body Parameters](#http-in-trunk-settings-body) section appears for `POST` and `PUT` only. |
| Validate HTTPS Certificate | Optional | Validates the TLS certificate of the destination server. Default: on. |
| Follow redirect | Optional | Follows redirects when the server responds with a `3xx` status code. Default: off. |
| Request URL | Required | URL of your web server or application endpoint, in the format `SCHEME://HOST[:PORT][PATH]`. For example, `https://example.com/sms`. |
| Query Parameters | Optional | Key-value pairs added to the request URL. Click **Add Parameter** to add a pair. Each added pair requires a **Key** and a **Value**. Click **×** to remove a pair. |
| Headers | Optional | Custom HTTP headers sent with the request. Click **Add Header** to add a header. Each added header requires a **Key** and a **Value**. Click **×** to remove a header. |

### Body parameters

The **Body Parameters** section defines the body of `POST` and `PUT`
requests.

| Field | Availability | Description |
| --- | --- | --- |
| Body type | Required for `POST` and `PUT` | Format of the request body. See [Body type values](#http-in-trunk-settings-body-types). |
| Request body | Required for **JSON** and **RAW** | Content of the request body. For example, `{"SMS-Time":"{SMS_TIME}","SMS-Text":"{SMS_TEXT}"}`. |
| Key and Value | Required for **HTML Multipart** and **HTML URL Encoded** | Body parameters sent as key-value pairs. Click **Add Parameter** to add a pair, or **×** to remove one. |

Body type values





| Value | Body format | Body fields |
| --- | --- | --- |
| JSON | JSON object (`application/json`) | **Request body** |
| HTML Multipart | Key-value pairs (`multipart/form-data`) | **Key** and **Value** pairs |
| HTML URL Encoded | Key-value pairs (`application/x-www-form-urlencoded`) | **Key** and **Value** pairs |
| RAW | Raw, unformatted payload | **Request body** |

### Request variables

You can use the following variables in the **Request URL**, **Query
Parameters**, **Headers**, and request body to customize the request. Each
variable is replaced with the corresponding value from the received SMS.

| Variable | Description | Example |
| --- | --- | --- |
| `{SMS_UUID}` | The unique ID of the received message. | `550e8400-e29b-41d4-a716-446655440000` |
| `{SMS_TIME}` | The time the SMS was received, in UTC. | `Thu, 22 Oct 2026 07:32:14 GMT` |
| `{SMS_SRC_ADDR}` | The sender address. A phone number is shown in international format without the plus sign. Some senders use an alphanumeric sender ID instead of a phone number. | `15551234567` |
| `{SMS_DST_ADDR}` | The DID number that received the SMS, in international format without the plus sign. | `15557654321` |
| `{SMS_TEXT}` | The raw text of the SMS message. For a long SMS sent in several parts, the complete, reassembled text. See [Technical details](../technical-data/http-specification.html#sms-in-spec-technical). | `Hello World!` |
| `{SMS_TEXT_BASE64_ENCODED}` | The SMS message text encoded in Base64. | `SGVsbG8gV29ybGQh` |

The variables box in the trunk form lists all variables except
`{SMS_UUID}`, which is also supported. For the request properties and the
DIDWW source IP addresses, see the [Inbound SMS
specification](../technical-data/http-specification.html#sms-in-specification).

## Trunk group settings

The optional **Trunk Group Configuration** section assigns the trunk to an
existing [SMS trunk group](../trunk-groups/sms-trunk-groups.html).

| Field | Availability | Description |
| --- | --- | --- |
| Assign to trunk group | Optional | Existing SMS trunk group to which the trunk is assigned. |
| Priority | Optional | Priority of the trunk within the selected trunk group. It determines the order in which trunks will be used. The system attempts to contact the target SMS trunk with the highest-numbered priority first. Trunks with the same priority are tried in a random order. Range: `0` to `32767`. Default: `1`. |

## Related resources

- [Create an HTTP IN trunk](how-to-guides/create-http-in-trunk.html) - Create
  a trunk and configure the settings described on this page.
- [Manage HTTP IN trunks](how-to-guides/manage-http-in-trunk.html) - Edit or
  delete an existing trunk.
- [HTTP IN trunk](http-in-trunk.html) - Understand how DIDWW delivers inbound
  SMS to your HTTP endpoint.
- [Inbound SMS specification](../technical-data/http-specification.html#sms-in-specification) - Review the request
  details, variables, body formats, and delivery behavior.
- [Assign an SMS trunk](../../../phone-numbers/my-numbers/how-to-guides/assign-sms-trunk.html#assigning-sms-trunk) - Assign the trunk to one
  or more DID numbers.
- [SMS trunk groups](../trunk-groups/sms-trunk-groups.html) - Group SMS
  trunks for failover.