# HTTP SMS Messenging

Enables ngSurvey to use any HTTP enabled SMS service provider.

## 🔅 HTTP properties

* **`Http endpoint URL`**is the endpoint of your provider that will be called each time ngSurvey needs to send an SMS message. You can use following tags that will be replaced dynamically in your URL if needed: {{to}} and {{message}}
* **`Http header 1`**will be sent as part of the request to the endpoint.
* **`Http header 2`**will be sent as part of the request to the endpoint.
* **`JWT Token`**if specified ngSurvey will attempt a "Bearer" based authentication.
* **`Http body`**is the body that will be send to to the endpoint if the endpoint requires a post.

If your provider requires an urlencoded content type for its post you may use and specify the settings like as follow:

<figure><img src="/files/nMkTjH48xnsN2vTxGGEt" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ngsurvey.com/installation-setup/system-settings/mobile-messenging/iis-smtp-exchange-server.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.