> 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/subscription-api-restful/sending-content-to-subscribers-api.md).

# Sending Content To Subscribers (API)

This document details how to send content/binary messages to your subscribers via RESTful api.

If you are using our content system you can also send your content directly to your subscribers via our RESTful api with the following **POST** request:&#x20;

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

```hsts
https://subscription-api.mobivate.com/subscriptions/v1/<campaign_id>/content
```

{% endtab %}

{% tab title="JSON Body" %}

```json
{
    "msisdn":"xxxxxxxxxxx"
    "keyword":"xxxxxxxx"
    "provider":"default"
    "cost":"100"
    "content":"1234567"
    "method":"sms"
    "signature":"xxxxxxxxxxxxxxxxxx"
}
```

{% endtab %}
{% endtabs %}

### Parameters

The only parameter you need to use in this api call is your content id as described below.&#x20;

| Parameter | Description                                                                                                                                      |
| --------- | ------------------------------------------------------------------------------------------------------------------------------------------------ |
| msisdn    | The unique **MSISDN** you are trying to unsubscribe.                                                                                             |
| keyword   | Your unique Mobivate keyword.                                                                                                                    |
| provider  | Network provider to use for the message. Can be either `default` or `premium`.                                                                   |
| cost      | The cost of the message to your subscriber, for example: `100`.                                                                                  |
| content   | The unique id for the content you want to send. For example: `1234567`.                                                                          |
| method    | The method of how users will access the content, can be either: `sms` or `url`.                                                                  |
| signature | Unique parameter consisting of three values: **campaign\_id**, **msisdn** and **account\_id**. For example:  `1af289e14aa593c843da7cd869a8e2f7`. |

### Successful response

If your user has been sent content successfully you will receive the following response, **HTTP Status Code 200**:

```json
{
  "authenticated" : True,
  "valid_msisdn" : True,
  "valid_campaign" : True,
  "campaign_status" : "active",
  "campaign_name" : "Test Campaign",
  "campaign_service" : "12345",
  "state" : "queued"
  "error" : Null,
  "reference": "AP:aaaaaaa-bbbbbbbbb-cccccccc"
}
```
