> For the complete documentation index, see [llms.txt](https://wiki.mobivate.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.mobivate.com/use-cases/receive-sms-via-http-mo-example.md).

# Receive SMS via HTTP (MO) Example

### <mark style="color:green;">`GET`</mark> `/yoursite.com.au/`

When an SMS MO message arrives at the SMS Gateway, it will send the following request to your application.

#### Example

<pre class="language-http"><code class="lang-http"><strong>http://www.yoursite.com.au/SMSfromMobiles?ORIGINATOR=61412345678&#x26;RECIPIENT=1987654&#x26;PROVIDER=telstra&#x26;MESSAGE_TEXT=Hello%20There&#x26;KEYWORD=&#x3C;KEYWORD>
</strong></code></pre>

#### Body

| Parameter     | Type    | Example       | Description                                       |
| ------------- | ------- | ------------- | ------------------------------------------------- |
| originator    | integer | 12345         | The associated shortcode for your service.        |
| recipient     | integer | XX7432104492  | The recipient you want to send this message to.   |
| provider      | string  | Telstra       | The network you plan to send the SMS message via. |
| message\_text | string  | Hello%20There | Your URL encoded message.                         |
| keyword       | string  | mv-100620006  | Your unique Mobivate keyword for your service.    |

#### Output

```json
{
 "ORIGINATOR": "61412345678",
 "RECIPIENT": "1987654",
 "PROVIDER": "telstra",
 "MESSAGE_TEXT": "Hello%20There",
 "KEYWORD": "<KEYWORD>"
}
```

#### Acknowledging MO's

For your endpoint to acknowledge MO's correctly your server needs to respond with a HTTP 200, and a body of either: “0” (ZERO), "OK" or "SUCCESS". To read more about this and see examples, [click here.](/use-cases/acknowledging-mos-and-drs.md)&#x20;

{% hint style="warning" %}
You need to provide us with the MO destination (URL) before we can provide you with an account credentials. Please contact your account manager.
{% endhint %}


---

# 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 dynamically by asking a question.

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

```
GET https://wiki.mobivate.com/use-cases/receive-sms-via-http-mo-example.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.