> 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/api-message-paramaters/receive-sms-mo-parameters.md).

# Receive SMS (MO) parameters

MO's should be returned to your MO endpoint in the following format:

```html
http://<your MOendpoint>?ORIGINATOR=MSISDN&CAMPAIGN=<campaign>&KEYWORD=<Keyword>&MESSAGE_TEXT=<incoming text>&REFERENCE=<Message-ID>&PROVIDER=<network>&RECIPIENT=<Shortcode>
```

When receiving SMS MO messages, the following parameters will be sent as part of the HTTP GET request:

| Parameter         | Description                                                                                                                                                                                         |
| ----------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **ORIGINATOR**    | Phone number of the originator (mobile phone) in international format (MSISDN) For example: `44700000000.`                                                                                          |
| **RECIPIENT**     | Service code / Shortcode number of the recipient.                                                                                                                                                   |
| **MESSAGE\_TEXT** | The SMS message sent by the Originator.                                                                                                                                                             |
| **PROVIDER**      | Identifies the telco provider (Telstra/Optus..)This field will be set to PREMIUM or left blank when receiving standard SMS messages For example: `Telstra.`                                         |
| **REFERENCE**     | The SMS Gateway will populate this parameter with our unique message identifier. Customers are encouraged to make sure no two messages are received with the same reference. For example: `ABC123.` |
| **VALUE**         | Billing amount in the lowest denomination of the currency. If “0” then the MO's are to be considered free to the sender.                                                                            |
| **KEYWORD**       | If applicable, the product/service keyword identified by the MNO.                                                                                                                                   |
| **CAMPAIGN**      | If applicable, the product/service campaign identified by the MNO.                                                                                                                                  |


---

# 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/api-message-paramaters/receive-sms-mo-parameters.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.