> For the complete documentation index, see [llms.txt](https://docs.ngsurvey.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ngsurvey.com/installation-setup/system-settings/mobile-messenging/iis-smtp-exchange-server.md).

# 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="https://1025048312-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-M8fLhS0bmfBRyq0HdUm%2Fuploads%2FmO9aTFSbLsixfjN521Rk%2Fimage.png?alt=media&amp;token=3299f1f9-6595-4902-9575-8a7d7af5e756" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.