> 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/send-silent-obs-billing-message-example.md).

# Send Silent OBS Billing Message Example

### <mark style="color:green;">`GET`</mark> `/srs/api/sendsms`

Send a silent OBS billing message and charge your end-user for it.&#x20;

{% hint style="warning" %}
This may not be available due to network regulations. For example, MTN hand their own billing requests.
{% endhint %}

{% tabs %}
{% tab title="Curl" %}

```hsts
curl -XGET -H "Content-type: application/json" 'https://hostname/srs/api/sendsms?USER_NAME=<account_id>&PASSWORD=<api_key>&ORIGINATOR=<SHORT CODE>&RECIPIENT=<MSISDN>&PR OVIDER=<Network Provider>&VALUE=<Amount>&KEYWORD=<Keyword>&MESSAGE_TEXT=SILENT%20BILLING%20MESSAGE'
```

{% endtab %}

{% tab title="Python" %}

```python
import requests

headers = {
    'Content-type': 'application/json',
}

response = requests.get(
    'https://hostname/srs/api/sendsms?USER_NAME=<account_id>&PASSWORD=<api_key>&ORIGINATOR=<SHORT CODE>&RECIPIENT=<MSISDN>&PR OVIDER=<Network Provider>&VALUE=<Amount>&KEYWORD=<Keyword>&MESSAGE_TEXT=SILENT%20BILLING%20MESSAGE',
    headers=headers,
)
```

{% endtab %}
{% endtabs %}

**Headers**

| Name          | Value              |
| ------------- | ------------------ |
| Content-Type  | `application/json` |
| Authorization | `No Auth`          |

**Body**

| Parameter     | Type    | Example                          | Description                                                   |
| ------------- | ------- | -------------------------------- | ------------------------------------------------------------- |
| account\_id   | string  | 43e36f50aaf111e272639171000000a9 | Your unique Mobivate account id.                              |
| password      | string  | 3b41d767316541bacef19d1382ac1e12 | Your unique associated Mobivate account api-key.              |
| originator    | integer | 12345                            | The associated shortcode for your service.                    |
| recipient     | integer | XX7432104492                     | The recipient you want to send this message to.               |
| provider      | string  | Safaricom                        | The network you plan to send the SMS message via.             |
| keyword       | string  | mv-100620006                     | Your unique Mobivate keyword for your service.                |
| message\_text | string  | SILENT%20BILLING%20MESSAGE       | Should be Silent Billing Message, end user will not see this. |
| value         | integer | 10                               | The cost of receiving this SMS message.                       |

**Response**

{% tabs %}
{% tab title="200" %}

```json
{
  "MT-aabbccddeeff00112233445566778899"
}
```

{% endtab %}

{% tab title="511" %}

```json
{
  "error": "Username or Password incorrect"
}
```

{% endtab %}
{% endtabs %}


---

# 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/send-silent-obs-billing-message-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.
