SMS API Banner

Trumpia REST API
Technical Guidelines

(Last Updated: 11/19/2014)
List
PUT Create a distribution list.
GET Retrieve information about your lists, including the list IDs, names, and parameters.
POST Update the parameters of a list.
DELETE Delete a list.
Subscription
PUT Create new subscriptions and associate them with existing distribution lists.
GET Lookup the IDs of the created subscriptions, or lookup detailed information for a subscription.
POST Update contact information of an existing subscription or associate a subscription to different distribution lists.
DELETE Permanently remove a subscription.
GET (Search) Lookup the IDs for relevant subscriptions by various search conditions, including name, phone number, email address, subscription created date, and more.
Message
PUT Send a mobile text (SMS, MMS), email, and/or IM message to specific subscription(s) or distribution list(s).
GET Retrieve the statistics of a successfully processed message, including the total numbers of target recipients, delivered and failed messages.
Keyword
PUT Create a mobile keyword and its auto-response message.
GET Lookup general information of existing mobile keywords, or detailed information of a keyword. For general information, keyword_id, keyword, and associated short code information is provided. For detailed information, keyword, auto-response message, associated short code, alternative message, and alternative coupon message are provided.
POST Update a mobile keyword and auto-response message.
DELETE Permanently remove a mobile keyword.
Publication
PUT Publish a status update to your feed on various publication targets, such as Facebook and/or Twitter.
GET Retrieve a summary of results for a publication post.
SNS Account
PUT Register a Facebook account, Facebook page, or Twitter account.
GET Retrieve a Facebook account, Facebook page, or Twitter account.
DELETE Permanently remove a Facebook account, Facebook page, or Twitter account.
Custom Data Field
PUT Create a custom data field.
GET Lookup the IDs of created custom data fields, or lookup detailed information for a specific custom data field.
POST Update the parameters of a custom data field.
DELETE Permanently remove a custom data field.
Number Identity
GET Look up the carrier of an existing mobile number.
Report
GET Report resource provides status report of a request.

List

A distribution list enables you to create a specific group of subscriptions. The list can then be used for targeted messaging or marketing campaigns, which means you are reaching only the most relevant subscribers.

PUT /rest/v1/{user_name}/list
GET /rest/v1/{user_name}/list
GET /rest/v1/{user_name}/list/{list_id}
POST /rest/v1/{user_name}/list/{list_id}
DELETE /rest/v1/{user_name}/list/{list_id}
PUT List

Create a distribution list by setting details such as list name, display name, frequency, and a description of the list. Upon submitting your request, the request ID and list ID will be returned so that you can track the request. After your request has been completely processed, a push notification will be sent to you indicating the success or failure of the request.

Once a distribution list is created, you can then add subscriptions to it by using the PUT Subscription request.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
list_name *
The name of your distribution list is case-insensitive but must contain only alphanumeric characters. The maximum length for a list name is 30 characters.
display_name *
The display name will be the name that your subscribers will see when signing up for your distribution list. As this name is public, make sure it makes sense to your future subscribers.
frequency *
The frequency of messages your subscribers receive each month must be disclosed, according to mobile industry regulations.
description *
The description of what types of messages your subscribers will receive when they opt into this list must be disclosed.
Request Example:
PUT http://api.trumpia.com/rest/v1/{user_name}/list
{ "list_name" : "listname0001", "display_name" : "display name", "frequency" : "2", "description" : "test list" }
Response Example:
{
  "request_id" : "1234561234567asdf123",
  "list_id" : "987987987980"
}
TOP
GET List

Lookup basic information, like list IDs and names, of existing distribution lists, or lookup detailed information of a specific distribution list.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example (all lists):
GET http://api.trumpia.com/rest/v1/{user_name}/list
Response Example:
{
  "list" : 
  [
    {
      "list_id" : "987987987980",
      "list_name" : "listname0001"
    },
    {
      "list_id" : "987987987981",
      "list_name" : "listname0002"
    },
    {
      "list_id" : "987987987982",
      "list_name" : "listname0003"
    }
  ]
}
Request Example (of a specific list):
GET http://api.trumpia.com/rest/v1/{user_name}/list/{list_id}
Response Example:
{
  "display_name" : "display name",
  "description" : "test list",
  "list_name" : "listname0001",
  "frequency" : "2",
  "subscription_count" : "0",
  "mobile_count" : "0",
  "im_count" : "0",
  "email_count" : "0"
}
TOP
POST List

Update the information, including the name, display name, frequency, and description, of a specific distribution list.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters
list_name
The name of your distribution list is case-insensitive but must contain only alphanumeric characters. The maximum length for a list name is 30 characters.
display_name
The display name will be the name that your subscribers will see when signing up for your distribution list. As this name is public, make sure it makes sense to your future subscribers.
frequency
The frequency of messages your subscribers receive each month must be disclosed, according to mobile industry regulations.
description
The description of what types of messages your subscribers will receive when they opt into this list must be disclosed.
Request Example:
POST http://api.trumpia.com/rest/v1/{user_name}/list/{list_id}
{ "list_name" : "listname0001", "display_name" : "display name", "frequency" : "2", "description" : "test list" }
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
DELETE List

Permanently remove a distribution list.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:
DELETE http://api.trumpia.com/rest/v1/{user_name}/list/{list_id}
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP

Subscription

Create a subscription record for a subscriber. This record is required for sending messages to the subscriber and most API requests.

It is important to note that API users must comply with our Terms of Use and industry privacy regulations, such as the CAN-SPAM act. Subscriptions should be added only with the expressed consent of the subscribers and that they be given the permission to opt-out, which is enabled by default with our text-messaging functions.

To synchronize the subscription database with external databases and be notified of subscriber opt-outs, inbound push must be set up.

PUT /rest/v1/{user_name}/subscription
GET /rest/v1/{user_name}/subscription
GET /rest/v1/{user_name}/subscription/{subscription_id}
POST /rest/v1/{user_name}/subscription/{subscription_id}
DELETE /rest/v1/{user_name}/subscription/{subscription_id}
GET /rest/v1/{user_name}/subscription/search
PUT Subscription

Create one or multiple subscriptions.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
list_name *
The distribution list(s) that the subscription is subscribed to.
subscriptions *
Subscriptions information must be provided for at least one of the following keys.
first_name
First name of the subscription.
last_name
Last name of the subscription.
voice_device
If the subscription needs to be reached out via voice, voice_device has to be specified. If voice_device is not specified, a voice message cannot be sent to the subscription.

Note:

Supported countries for voice are US, Canada, Guam and Puerto Rico.
The possible values for voice_device are 'Landline' and 'Mobile' . When you set the voice_device attribute, you must also register the respective landline or mobile information.

For example, if you register the mobile number instead of landline and set voice_device to 'Landline', then the voice message cannot be sent.
email
Email address of the subscription.
aim
AOL Instant Messenger screen name.
mobile

Note:

number is required if mobile is added.
number *
Mobile phone number.
country_code
Country code of the number. (Default: 1)
landline

Note:

number is required if landline is added.
number *
Landline phone number.
country_code
Country code of the number. (Default: 1)
customdata
Add custom data such as birthday, age, etc. This is created by Custom Data Field.
customdata_id *
Custom data field ID. You can get this via GET Custom Data Field.
value *
Custom data value. There are basic, differing restrictions for each type of custom data field. You can view this via GET Custom Data Field.

Field Type Description
Text Field This must contain only alphanumeric characters. You can get max_length via GET Custom Data Field.
Radio Button Enter a fixed value. You can get the fixed value via GET Custom Data Field.
Drop-down List Enter a fixed value. You can get the fixed value via GET Custom Data Field.
Date & Time Enter the value with this format:
- Date only Case : YYYY-MM-DD
- Date & Time Case : YYYY-MM-DD hh:mm:ss
Text Area This must contain only alphanumeric characters. Max_length is 4000 characters.
Number This must contain only numeric characters. You can get min and max value via GET Custom Data Field.
Request Example:
PUT http://api.trumpia.com/rest/v1/{user_name}/subscription
{ "list_name" : "listname0001,listname0002,listname0003", "subscriptions" : [ { "first_name" : "Subscriber's First Name", "last_name" : "Subscriber's Last Name", "email" : "subscriber_email0001@trumpia.com", "aim" : "aimname", "mobile" : { "number" : "2003004000", "country_code" : "1" }, "voice_device" : "mobile", "customdata" : [ { "customdata_id" : 987987987987, "value" : "Apple" }, { "customdata_id" : 987987987980, "value" : "2014-10-10 00:00:01" } ] }, { "first_name" : "Subscriber's First Name02", "email" : "subscriber_email0002@trumpia.com", "landline" : { "number" : "3004005000", "country_code" : "1" }, "voice_device" : "landline" } ] }
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
GET Subscription

Lookup the IDs of existing subscriptions in batches of 100, or lookup detailed information of a subscription.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Query String
row_size
Number of subscription IDs you want to retrieve. (Default: 100)
Request Example (up to 10 subscriptions):
GET http://api.trumpia.com/rest/v1/{user_name}/subscription?row_size=10
Response Example:
{
  "subscription_id_list" :
  [
    "987987987980","987987987981","987987987982","987987987983","987987987984","987987987985","987987987986","987987987987","987987987988","987987987989"
  ]
}
Request Example (for a specific subscription):
GET http://api.trumpia.com/rest/v1/{user_name}/subscription/{subscription_id}
Response Example:
{
  "list_ids" : 
  [
    "987987987980", "987987987981", "987987987982", "987987987983"
  ],
  "created_date" : "2012-02-27 18:05:33",
  "landline" :
  {
    "value" : "3004005000",
    "country_code" :1,
    "verified" : "true"
  },
  "email" :
  {
    "value" : "subscriber_email0001@trumpia.com",
    "verified" : "true"
  },
  "first_name" : "Subscriber's First Name",
  "customdata" : 
  [
    {
      "customdata_id" : 987987987987,
      "name" : "favorite fruit",
      "value" : "Apple"
    },
    {
      "customdata_id" : 987987987980,
      "name" : "birthday",
      "value" : "2014-10-10 00:00:01"
    }
  ]
}
TOP
POST Subscription

Update the contact information, such as name, phone number, email address, and distribution list, for an existing subscription.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters
list_name
To change the distribution list(s) that the subscription is subscribed to, update this parameter.

Note:

Specifying the list name(s) will assign the subscription to only the list(s) regardless of where the subscription originally belonged to.

subscriptions

Note:

In case you are deleting specific data from a subscription, put "delete" as the value to the desired parameter.

first_name
First name of the subscription.
last_name
Last name of the subscription.
email
Email address of the subscription.
aim
AOL Instant Messenger screen name.
mobile

Note:

After successful update, number must exist if mobile exists on the subscription.
number
Mobile phone number.
country_code
Country code of the number. (Default: 1)
landline

Note:

After successful update, number must exist if landline exists on the subscription.
number
Landline phone number.
country_code
Country code of the number. (Default: 1)
customdata
Add custom data such as birthday, age, etc. This is created by Custom Data Field.
customdata_id *
Custom data field ID. You can get this via GET Custom Data Field.
value *
Custom data value. There are basic, differing restrictions for each type of custom data field. You can view this via GET Custom Data Field.

Field Type Description
Text Field This must contain only alphanumeric characters. You can get max_length via GET Custom Data Field.
Radio Button Enter a fixed value. You can get the fixed value via GET Custom Data Field.
Drop-down List Enter a fixed value. You can get the fixed value via GET Custom Data Field.
Date & Time Enter the value with this format:
- Date only Case : YYYY-MM-DD
- Date & Time Case : YYYY-MM-DD hh:mm:ss
Text Area This must contain only alphanumeric characters. Max_length is 4000 characters.
Number This must contain only numeric characters. You can get min and max value via GET Custom Data Field.
Request Example:
POST http://api.trumpia.com/rest/v1/{user_name}/subscription/{subscription_id}
{ "list_name" : "listname0001,listname0002,listname0003", "subscriptions" : [ { "first_name" : "Subscriber's First Name", "last_name" : "Subscriber's Last Name", "email" : "subscriber_email0001@trumpia.com", "aim" : "aimname", "mobile" : { "number" : "2003004000", "country_code" : "1" }, "customdata" : [ { "customdata_id" : 987987987987, "value" : "Apple" }, { "customdata_id" : 987987987980, "value" : "2014-10-10 00:00:01" } ] } ] }
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
DELETE Subscription

Permanently remove a subscription.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:
DELETE http://api.trumpia.com/rest/v1/{user_name}/subscription/{subscription_id}
Response Example:
{
  "message" : "Success Delete Subscription",
  "subscription_id" : 987987987980
}
TOP
GET Search Subscription

Search for subscription IDs by various data types, including first or last name, phone number, email address, date the account was created, and more.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Query String * required parameters
search_type *
Type of subscription data to search for your subscription by.
Value Description Value Description
1 Email 102 Country code
2 Mobile 103 Created date
3 Landline 104 First name
4 AIM 105 Last name
search_data *
Based on the search_type selected above, you must provide the appropriate data. For example, if you would like to search for a specific subscription ID by email, set search_type=1 and provide that contact's email address for search_data, such as search_data=johndoh@mail.com. If you would like to retrieve all the subscription IDs for which there are data for particular search types, for example all subscriptions with email addresses, set search_data=all. This feature only works for search types 1-4.

For searching by created date (i.e., search_type=103), the search_data must be in the format: YYYY-MM-DD hh:mm:ss~YYYY-MM-DD hh:mm:ss (ex: 2013-03-01 13:00:00~2013-04-01 13:00:00). To search over a date range, use the character "~" between the two dates.
Note: YYYY = four-digit year
MM = two-digit month (01=January, etc.)
DD = two-digit day of month (01 through 31)
hh = two digit hours (00 through 23; am/pm NOT allowed)
mm = two digit minutes (00 through 59)
ss = two digit seconds (00 through 59)
list_id
You may limit the search to a specific distribution list.
Request Example (search for one subscription ID by email address):

The following example includes the parameters and values necessary to search for the subscription with the email address johndoh@mail.com from the distribution list 12345.

GET http://api.trumpia.com/rest/v1/{user_name}/subscription/search?search_type=1&search_data=johndoh@mail.com&list_id=12345
Response Example:

The desired subscription ID will be sent back to your designated URL:

{
  "subscription_id_list" :
  [
    "987987987980"
  ]
}
Request Example (search for all subscription IDs by phone number):

To search your entire database for all the subscriptions that have a landline phone number saved, you would submit the following call:

GET http://api.trumpia.com/rest/v1/{user_name}/subscription/search?search_type=3&search_data=all
Response Example:

The subscription IDs for all the relevant subscriptions will be returned:

{
  "subscription_id_list" :
  [
    "987987987980","987987987981","987987987982","987987987983","987987987984","987987987985","987987987986","987987987987"
  ]
}
TOP

Message

Send a message via supported communication channels, including mobile-text message (SMS/MMS), email, or instant message.

It is important to note that API users must comply with our Terms of Use and industry privacy regulations, such as the CAN-SPAM act. Subscriptions should be added only with the expressed consent of the subscribers and that they be given the permission to opt-out, which is enabled by default with our text-messaging functions.

PUT /rest/v1/{user_name}/message
GET /rest/v1/{user_name}/message/{message_id}
PUT Message

To send a message, you will need to provide the ID of the subscription or distribution list(s) you wish to message.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
description *
description of your message for your reference.
email

Note:

subject and body are required if email is added.
subject *
email subject.
body *
Email content.

You can add mail merge data such as first name and last name. Mail Merge Data Format is below.
Data Input Value
First Name [$FirstName]
Last Name [$LastName]

If you don't enter the proper input value for mail merge data, our system will recognize the input value as text instead of mail merge data. As a result, you may get a status code referencing unsupported characters due to '[', ']'.
reply_to
reply_to address.
im

Note:

message is required if IM is added.
message *
IM message.
sms / mms (select one)
sms

Note:

message is required if sms is added.
message *
SMS message. Supported Character Set.
Character limits vary per country. The maximum length for a message is 160 characters as default. For instance, SMS messages for Canadian accounts are limited to 140 characters. Although a 160 character message can be sent in full to US mobile numbers, Canadian mobile devices will only receive the first 140 characters.

Also, please note that the SMS header and footer are counted as part of the message and should be taken into consideration when composing a message.

You can add mail merge data such as first name and last name. Mail Merge Data Format is below.
Data Input Value
First Name [$FirstName]
Last Name [$LastName]

If you don't enter the proper input value for mail merge data, our system will recognize the input value as text instead of mail merge data. As a result, you may get a status code referencing unsupported characters due to '[', ']'.
mms

Note:

message is required if mms is added.
subject
MMS subject line; character limit is 50 bytes. Supported Character Set.
message *
MMS message; character limit is 500 bytes. Supported Character Set.
You can add mail merge data such as first name and last name. Mail Merge Data Format is below.
Data Input Value
First Name [$FirstName]
Last Name [$LastName]

If you don't enter the proper input value for mail merge data, our system will recognize the input value as text instead of mail merge data. As a result, you may get a status code referencing unsupported characters due to '[', ']'.
resource
Resource URL required. Image size limit is 500 KB; supported image file types include .JPG, .PNG, .GIF (non-animated), .BMP; Video size limit is 3 MB; supported video file types include .AVI, .MP4, .WMV, and .MOV. Click here for the list of supported audio and video codecs.
recipients *
type *
list or subscription.
value *
list IDs or subscription IDs.
mail_merge
Mail merge is the replacement value for null data if the content contains mail merge variables, such as first name and last name.
first_name
If you added first_name in the message content, you can set this as replacement text. When the subscriber's data is null, then this value will be used.
last_name
If you added last_name in the message contents, you can set this as replacement text. When the subscriber's data is null, then this value will be used.
send_date
YYYY-MM-DD hh:mm:ss (ex: 2009-04-22 14:10:32)
Note: YYYY = four-digit year
MM = two-digit month (01=January, etc.)
DD = two-digit day of month (01 through 31)
hh = two digit hours (00 through 23; am/pm NOT allowed)
mm = two digit minutes (00 through 59)
ss = two digit seconds (00 through 59)
Request Example:
PUT http://api.trumpia.com/rest/v1/{user_name}/message

{
  "description" : "This is a description",
  "email" : 
  {
    "subject" : "Hello [$FirstName], REST API is here!",
    "body" : "Contact support for more info."
  },
  "sms" : 
  {
    "message" : "Hello [$LastName], REST API is out now!"
  },
  "recipients" : 
  {
    "type" : "list",
    "value" : "987987987980, 9879879879801"
  },
  "mail_merge" : 
  {
    "first_name" : "Jason",
    "last_name" : "Bone"
  }
}
Response Example:
{
  "request_id" : "1234561234567asdf123",
  "message_id" : "987987987987"
}
TOP
GET Message

Retrieve the statistics of a successfully processed message, including the total numbers of target recipients, delivered and failed messages.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:
GET http://api.trumpia.com/rest/v1/{user_name}/message/{message_id}
Response Example:

The following examples are for message blasts that include SMS. For blasts that include MMS, the only difference will be that the "sms" parameter will be called "mms".

  • 1) In case of sending a message that includes a coupon:
    • a) sending / sent / failed status
{
  "status" : "sent",
  "email" : {"total" : 5,"sent" : 2,"failed" : 3},
  "sms" : {"total" : 5,"sent" : 5,"failed" : 0},
  "im" : {"total" : 5,"sent" : 1,"failed" : 4},
  "coupon" :
  [
    {"coupon_code" : "9pao8e98l9s0","subscription" : "6666666"},
    {"coupon_code" : "ap9o8e9979sa","subscription" : "7777777"},
    {"coupon_code" : "a03ui49s83a8","subscription" : "8888888"},
    {"coupon_code" : "afn209z7va2f","subscription" : "9999999"},
    {"coupon_code" : "ginz921x3482","subscription" : "0000000"}
  ]
}
    • b) scheduled status
{
  "status" : "scheduled",
  "email" : {"total" : 5,"sent" : 0,"failed" : 0},
  "sms" : {"total" : 5,"sent" : 0,"failed" : 0},
  "im" : {"total" : 5,"sent" : 0,"failed" : 0},
  "coupon" :
  [
    {"coupon_code" : "9pao8e98l9s0","subscription" : "6666666"},
    {"coupon_code" : "ap9o8e9979sa","subscription" : "7777777"},
    {"coupon_code" : "a03ui49s83a8","subscription" : "8888888"},
    {"coupon_code" : "afn209z7va2f","subscription" : "9999999"},
    {"coupon_code" : "ginz921x3482","subscription" : "0000000"}
  ]
}
  • 2) In case of sending a message that includes a coupon:
{
  "status" : "sent",
  "email" : {"total" : 2,"sent" : 2,"failed" : 0},
  "sms" : {"total" : 1,"sent" : 1,"failed" : 0}
}
TOP

Keyword

A mobile keyword enables API users to collect new subscriptions automatically through any SMS-enabled mobile phone. An auto-response message can also be set up that is sent to new subscribers after texting in the keyword. Parameter values can be set so that you can receive an inbound push notification by email or SMS whenever the keyword is texted in.

PUT /rest/v1/{user_name}/keyword
GET /rest/v1/{user_name}/keyword
GET /rest/v1/{user_name}/keyword/{keyword_id}
POST /rest/v1/{user_name}/keyword/{keyword_id}
DELETE /rest/v1/{user_name}/keyword/{keyword_id}
PUT Keyword

Set up your mobile keyword by providing the following parameters.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
keyword *
Enter the name of your mobile keyword.
lists *
The list that subscriptions will be added to.
allow_message *
Valid value is TRUE or FALSE. This enables users to add their own message or response after the keyword. This message will be sent to your Inbox.
auto_response *
Configure the settings of your auto-response message.

Character limits vary per country. The maximum length for a message is 160 characters as default. For instance, SMS messages for Canadian accounts are limited to 140 characters. Although a 160 character message can be sent in full to US mobile numbers, Canadian mobile devices will only receive the first 140 characters.

Also, please note that the SMS header and footer are counted as part of the message and should be taken into consideration when composing a message.

message *
The content of your auto-response message. Supported Character Set.
frequency (default "1")
The number of times an auto-response message will be delivered when a user texts in the keyword.
Value Description
1 everytime
2 only once per mobile number
3 only once every day
alternative_message
The content of an alternative auto-response message. This message will be sent if a user texts in the keyword more than once. Supported Character Set.
alternative_coupon
This alternate message will be sent to your user in case you have run out of coupon codes. To set up a coupon code to be inserted into the message of your auto-response or alternative_message, you must login to your account dashboard.
notify
Configure to be notified of any messages from your users.

Note:

subscription is required if notify is added.
email (Either email or mobile must be set.)
Email address to where a notification will be sent when a person signs up via this keyword.
mobile (Either email or mobile must be set.)
Mobile phones to where a notification will be sent when a person signs up via this keyword.
subscription *
Valid value is all or new.
Value Description
all Notify for all subscriptions.
new Notify only when the subscriber's mobile number is new to your subscription database.
Request Example:
PUT http://api.trumpia.com/rest/v1/{user_name}/keyword
{ "keyword" : "testKeyword", "lists" : "987987987980,987987987981", "allow_message" : "true", "auto_response" : { "frequency" : "2", "message" : "hi this is auto response message", "alternative_message" : "welcome back :)" }, "notify" : { "email" : "subscriber_email0001@trumpia.com", "mobile" : "2003004000", "subscription" : "new" } }
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
GET Keyword

Lookup general information about your mobile keywords, including ID, name, and short code, or more detailed information, like auto-response message, for an individual keyword.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example (to retrieve general information for all your keywords):
GET http://api.trumpia.com/rest/v1/{user_name}/keyword
Response Example:
{
  "keyword" :
  [
    {"keyword_id" : "987987987980","keyword" : "testKeyword","shortcode" : "95577"},
    {"keyword_id" : "987987987981","keyword" : "testKeyword","shortcode" : "95577"},
    {"keyword_id" : "987987987982","keyword" : "testKeyword","shortcode" : "95577"}
  ]
}
Request Example (to retrieve complete information for a specific keyword):
GET http://api.trumpia.com/rest/v1/{user_name}/keyword
Response Example:
{
  "keyword" : "testKeyword",
  "auto_response_message" : "This is the keyword message.",
  "shortcode" : "95577",
  "alternative_message" : "Hi there!",
  "alternative_coupon" : "This is the alternative coupon message."
}
TOP
POST Keyword

Update your mobile keyword and auto-response message. All values can be changed except for the name of your keyword (i.e., "keyword" parameter).

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters
lists
The list that subscriptions will be added to.
allow_message
Valid value is TRUE or FALSE. This enables users to add their own message or response after the keyword. This message will be sent to your Inbox.
auto_response
Configure the settings of your auto-response message.

Character limits vary per country. The maximum length for a message is 160 characters as default. For instance, SMS messages for Canadian accounts are limited to 140 characters. Although a 160 character message can be sent in full to US mobile numbers, Canadian mobile devices will only receive the first 140 characters.

Also, please note that the SMS header and footer are counted as part of the message and should be taken into consideration when composing a message.

message
The content of your auto-response message. Supported Character Set.
frequency (default "1")
The number of times an auto-response message will be delivered when a user texts in the keyword.
Value Description
1 everytime
2 only once per mobile number
3 only once every day
alternative_message
The content of an alternative auto-response message. This message will be sent if a user texts in the keyword more than once. Supported Character Set.
alternative_coupon
This alternate message will be sent to your user in case you have run out of coupon codes. To set up a coupon code to be inserted into the message of your auto-response or alternative_message, you must login to your account dashboard.
notify
Configure to be notified of any messages from your users.

Note:

After successful update, subscription must exist if notify exists on the keyword.
After successful update, either email or mobile must exist if notify exists on the keyword.
email (Either email or mobile must be set.)
Email address to where a notification will be sent when a person signs up via this keyword.
mobile (Either email or mobile must be set.)
Mobile phones to where a notification will be sent when a person signs up via this keyword.
subscription
Valid value is all or new.
Value Description
all Notify for all subscriptions.
new Notify only when the subscriber's mobile number is new to your subscription database.
Request Example:
POST http://api.trumpia.com/rest/v1/{user_name}/keyword/{keyword_id}
{ "notify" : { "email" : "subscriber_email0001@trumpia.com", "mobile" : "2003004000" } }
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
DELETE Keyword

Permanently remove a mobile keyword.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:
DELETE http://api.trumpia.com/rest/v1/{user_name}/keyword/{keyword_id}
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP

Publication

Publish content to various social networking platforms, including Facebook and Twitter. Before sending a publication call, you must connect your social networking accounts to your Trumpia account by logging into My Account > Social Networking Accounts. You may add multiple social networking accounts for publishing a status update for any number of accounts.

PUT /rest/v1/{user_name}/publication
GET /rest/v1/{user_name}/publication/{publication_id}
PUT Publication

Post a status update on Facebook and a tweet on Twitter simultaneously. Privacy for Facebook posts can be set to various levels, including everyone, friends of friends, or friends only. Links, images, or videos can be shared, given the URL. Both Facebook and Twitter posts can be scheduled for a specific date and time.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
description *
Description of your post for your reference.
twitter

Note:

tweet and account_names are required if twitter is added.
tweet *
Content of Twitter status update. Maximum length is 140 characters.
account_names *
Name(s) of the Twitter account(s) to post the tweet to. Multiple accounts can be listed separated by commas.

Note:

The account(s) must be linked to your Trumpia account.
facebook

Note:

post and account_names are required if facebook is added.
post *
Content of Facebook status update. Maximum length is 4,000 characters.
account_names *
Name(s) of the Facebook account(s) to post the status update to. Multiple accounts can be listed separated by commas.

Note:

The account(s) must be linked to your Trumpia account.
privacy
Control who can see your message. For more information on Facebook's privacy settings, visit its Data Use Policy page. Only one value may be selected.
Value Description
1 Everyone(default)
2 Friends of Friends
3 Friends only
attachment

Note:

type and url are required if attachment is added.
type *
Share media, like a video or image, or a web link in your status update. Only one value may be selected.
Value Description
2 Link
3 Image
4 Video
url *
Provide the URL to the shared web link or where your video or image is hosted.

Note:

The URL must include "http://".
facebook_page

Note:

post and account_names are required if facebook page is added.
post *
Content of Facebook status update. Maximum length is 4,000 characters.
account_names *
Name(s) of the Facebook account(s) to post the status update to. Multiple accounts can be listed separated by commas.

Note:

The account(s) must be linked to your Trumpia account.
privacy
Control who can see your message. For more information on Facebook's privacy settings, visit its Data Use Policy page. Only one value may be selected.
Value Description
1 Everyone (default)
2 Friends of Friends
3 Friends only
attachment

Note:

type and url are required if attachment is added.
type *
Share media, like a video or image, or a web link in your status update. Only one value may be selected.
Value Description
2 Link
3 Image
4 Video
url *
Provide the URL to the shared web link or where your video or image is hosted.

Note:

The URL must include "http://". Maximum video size is 1024 MB.
post_date
Date and time to post the status update. If these values are not provided, the post will be published immediately. Valid format is YYYY-MM-DD hh:mm:ss (ex: 2013-05-29 14:10:32).
Note: YYYY = four-digit year
MM = two-digit month (01=January, etc.)
DD = two-digit day of month (01 through 31)
hh = two digit hours (00 through 23; am/pm NOT allowed)
mm = two digit minutes (00 through 59)
ss = two digit seconds (00 through 59)
Request Example:

In the following example, three types of social-network status updates are submitted simultaneously: Twitter, Facebook, and Facebook Page.

The first parameter value that is required to be set is the description, which serves as a reference as to the purpose of this request. Next in the template, a simple Twitter status update, or tweet, is posted to four different Twitter accounts. The following Facebook status update is also posted to four different Facebook accounts with the privacy parameter set to 2, which allows Friends of Friends to see the post. The post also includes an attachment type of 3, an image, whose web location is provided for the URL parameter. Posting to a Facebook Page is similar, except that in this example, an AVI video is included in the post.

Finally, the post_date, or when these updates are published, is set to May 22, 2013 at 8:00 pm.

PUT http://api.trumpia.com/rest/v1/{username}/publication
{ "description" : "This is a description", "twitter" : { "tweet" : "Hello~! Twitter", "account_names" : "twitter_acc_01, twitter_acc_02, twitter_acc_03" }, "facebook" : { "post" : "Hello~! Facebook", "account_names" : "fb.account01, fb.account02, fb.account03", "privacy" : "2", "attachment" : { "type" : "3", "url" : "http://yourdomain.com/image.png" } }, "facebook_page" : { "post" : "Hello~! Facebook Page", "account_names" : "fb.page.account01, fb.page.account02, fb.page.account03", "privacy" : "3", "attachment" : { "type" : "4", "url" : "http://yourdomain.com/video.avi" } }, "post_date" : "2013-05-22 20:00:00" }
Response Example:

The request_id and publication_id are returned, which shows that the API request has been successfully submitted. The request_id can be used with GET Status Report request to retrieve summary results.

{
  "request_id" : "1234561234567asdf123",
  "publication_id" : "987987987987"
}
TOP
GET Publication

Retrieve the summary results of a PUT Publication request, including the total number of status updates submitted, the number of successful updates, and the number of failed updates.

Sample Codes
Request Example:
GET http://api.trumpia.com/rest/v1/{user_name}/publication/{publication_id}
Response Example:

The values of the status parameter can be either scheduled, posting(i.e., in progress) or posted(i.e., completed).

{
  "status" : "posted",
  "twitter" :
  {
    "total" : 5,
    "posted" : 2,
    "failed" : 3
  },
  "facebook" :
  {
    "total" : 5,
    "posted" : 5,
    "failed" : 0
  },
  "facebook_page" :
  {
    "total" : 5,
    "posted" : 1,
    "failed" : 4
  }
}
TOP

SNS Account

You should register your social networking account(s) and page(s) before publishing content. You can register your Facebook account, Facebook page, or Twitter account.

PUT /rest/v1/{user_name}/account/sns
GET /rest/v1/{user_name}/account/sns
GET /rest/v1/{user_name}/account/sns/{sns_id}
GET /rest/v1/{user_name}/account/sns/{sns_id}/page
GET /rest/v1/{user_name}/account/sns/{sns_id}/page/{page_id}
DELETE /rest/v1/{user_name}/account/sns/{sns_id}
DELETE /rest/v1/{user_name}/account/sns/{sns_id}/page/{page_id}
PUT SNS Account

Register a Facebook account, Facebook page, or Twitter account.

When you perform a PUT SNS Account, you will receive an authentication_url. After logging into Facebook or Twitter via the authentication_url, you can complete the register process. You can then verify if the request was successful.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
service *
The type of SNS service. Valid value is facebook, twitter, or facebook_page. The service is case-insensitive.

Note:

facebook_page_id is required if the service is "facebook_page".
facebook_page_id
A number value. ^[1-9][0-9]{0,17}$
This is the unique ID created by Facebook. You can find this ID within the Facebook page's Info page.
Request Example: Register a facebook or twitter account.
PUT http://api.trumpia.com/rest/v1/{user_name}/account/sns
{ "service" : "facebook" }
Response Example:
{
  "request_id" : "1234561234567asdf123",
  "authentication_url" : "https://www.facebook.com/oauth?get_info.php"
}
Request Example: Register a facebook page.
PUT http://api.trumpia.com/rest/v1/{user_name}/account/sns
{ "service" : "facebook_page", "facebook_page_id" : "456456456000" }
Response Example:
{
  "request_id" : "1234561234567asdf123",
  "authentication_url" : "https://www.facebook.com/oauth?get_info.php"
}
TOP
GET SNS Account

Lookup basic information(SNS IDs and names of existing Facebook accounts, Facebook pages, or Twitter accounts), or lookup detailed information of a specific account and page.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example: Get all lists of Facebook accounts, Facebook pages, and Twitter accounts.
GET http://api.trumpia.com/rest/v1/{user_name}/account/sns
Response Example:
{
  "facebook_id_list" :
  [
    "987987987980", "987987987981"
  ],
  "twitter_id_list" :
  [
    "987987987982", "987987987983", "987987987984", "987987987985"
  ]
}
Request Example: Get a specific Facebook or Twitter account.
GET http://api.trumpia.com/rest/v1/{user_name}/account/sns/{sns_id}
Response Example:
{
  "service" : "facebook",
  "sns_name" : "fb.account01"
}
Request Example: Get a Facebook page or set of pages associated with a specific Facebook account.
GET http://api.trumpia.com/rest/v1/{user_name}/account/sns/{sns_id}/page
Response Example:
{
  "facebook_page_id_list" :
  [
    "456456456000", "456456456001", "456456456002", "456456456003" 
  ]
}
Request Example: Get a specific Facebook page.
GET http://api.trumpia.com/rest/v1/{user_name}/account/sns/{sns_id}/page/{page_id}
Response Example:
{
  "service" : "facebook_page",
  "page_name" : "fb.account01",
  "facebook_id" : "987987987980"
}
TOP
DELETE SNS Account

Permanently remove a Facebook account, Facebook page, or Twitter page.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example: Delete a specific Facebook or Twitter account.
DELETE http://api.trumpia.com/rest/v1/{user_name}/account/sns/{sns_id}
Request Example: Delete a specific Facebook page.
DELETE http://api.trumpia.com/rest/v1/{user_name}/account/sns/{sns_id}/page/{page_id}
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP

Custom Data Field

You can create and use custom data fields for collecting extra information from subscribers. First, you will use PUT Custom Data Field to create a new field. Then, use PUT and POST Subscription to add your custom data. You can create up to 10 different custom data fields.

PUT /rest/v1/{user_name}/customdata
GET /rest/v1/{user_name}/customdata
GET /rest/v1/{user_name}/customdata/{customdata_id}
POST /rest/v1/{user_name}/customdata/{customdata_id}
DELETE /rest/v1/{user_name}/customdata/{customdata_id}
PUT Custom Data Field

Set up a custom data field by providing the parameters provided below. You can set up six types of custom data fields: Text Field, Radio buttons, Drop-down list, Date/Time, Text Area, and Number. You can have up to 10 custom data fields at a time.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters * required parameters
name *
The name for the specific Custom Data Field. A name can only be 3-30 characters in length. This is case-insensitive but must contain alphanumeric characters and only a few special characters such as (, ), /, -, and space.
input_type *
The input type for the specific Custom Data Field.
Value Description
1 Text Field
3 Radio Buttons
4 Drop-down List
5 Date & Time
6 Text Area
7 Number
required *
You can make a custom data field required or not for a new Online Signup Page subscriber. Custom fields will still be optional if you update the data via PUT/POST Subscription.
Value Description
1 Required
2 Optional

options *
These are other setting options for the Custom Data Field. Each type contains different options.

Input Type : Text Field

width *
This is the UI option for the Online Signup Page. Width value should be 1-239 pixels and should only be a numeric value.
max_length *
The maximum allowed length of the inputted text. Max_length value should be 1-4000 and should only be a numeric value.

Input Type : Radio Button

values *
Valid values for this custom data field. You can register up to 10 values.

Input Type : Drop-down List

values *
Valid values for this custom data. You can register up to 100 different values.

Input Type : Date & Time

time *
You can set 'Date Only' or 'Date & time'.
Value Description
1 Date Only
2 Date & Time

Input Type : Text Area

width *
This is the UI option for Online Signup Page. Width value should be 1-239 pixels and should be a numeric value.
rows *
This is the UI option for Online Signup Page. Width value should be 1-9 rows and should be a numeric value.

Input Type : Number

min *
Minimum number value. Min value should be numerical over 0.
max *
Maximum number value. Max value should be numerical under 9,999,999.
default *
Default number value.
Request Example: Text Field Case
PUT http://api.trumpia.com/rest/v1/{user_name}/customdata

{
  "name" : "School",
  "input_type" : 1,
  "required" : 1,
  "options" : 
  {
    "width" : 100,
    "max_length" : 300
  }
}
Request Example: Radio Button Case
PUT http://api.trumpia.com/rest/v1/{user_name}/customdata

{
  "name" : "Favorite Brand",
  "input_type" : 3,
  "required" : 2,
  "options" : 
  { 
    "values" :
    [
      "Jaguar", "BMW", "KIA"
    ]
  }
}
Request Example: Drop-down List Case
PUT http://api.trumpia.com/rest/v1/{user_name}/customdata

{
  "name" : "Car Brand",
  "input_type" : 4,
  "required" : 1,
  "options" : 
  { 
    "values" :
    [
      "Jaguar", "BMW", "KIA"
    ]
  }
}
Request Example: Date & Time Case
PUT http://api.trumpia.com/rest/v1/{user_name}/customdata

{
  "name" : "Birthday",
  "input_type" : 5,
  "required" : 1,
  "options" : 
  { 
    "time" : 1
  }
}
Request Example: Text Area Case
PUT http://api.trumpia.com/rest/v1/{user_name}/customdata

{
  "name" : "Self Introduce",
  "input_type" : 6,
  "required" : 2,
  "options" : 
  { 
    "width" : 100,
    "rows" : 5
  }
}
Request Example: Number Case
PUT http://api.trumpia.com/rest/v1/{user_name}/customdata

{
  "name" : "Age",
  "input_type" : 7,
  "required" : 1,
  "options" : 
  { 
    "min" : 17,
    "max" : 100,
    "default" : 20 
  } 
}
Request Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
GET Custom Data Field

Look up the IDs of created custom data fields, or look up detailed information for a custom data field.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example: Get all lists of custom data fields.
GET http://api.trumpia.com/rest/v1/{user_name}/customdata
Request Example:
{
  "customdata" : 
  [
    {
      "customdata_id" : 987987987980,
      "name" : "school"
    },
    {
      "customdata_id" : 987987987981,
      "name" : "favorite fruit"
    },
    {
      "customdata_id" : 987987987982,
      "name" : "birthday"
    }
  ]
} 
Response Example: Get a specific custom data fields.
GET http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}
Response Example:
{
  "customdata_id" : 987987987980,
  "name" : "School",
  "input_type" : 1,
  "required" : 1,
  "options" : 
  {
    "width" : 100,
    "max_length" : 300
  }
}
TOP
POST Custom Data Field

Update the parameters of a custom data field.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Body Parameters
required
You can make a custom data field required or not for a new Online Signup Page subscriber. Custom fields will still be optional if you update the data via PUT/POST Subscription.
Value Description
1 Required
2 Optional

options
This is other setting options for the Custom Data Field. Each type will have different options.

Input Type : Text Field

width
This is the UI option for Online Signup Page. Width value should be 1-239 pixels and should be a numeric value.

Input Type : Radio Button

values
Valid values for this custom data field. You can register up to 10 values.

Input Type : Drop-down List

values
Valid values for this custom data. You can register up to 100 different values.

Input Type : Date & Time

time
You can set 'Date Only' or 'Date & time'.
Value Description
1 Date Only
2 Date & Time

Input Type : Text Area

width
This is the UI option for Online Signup Page. Width value should be 1-239 pixels and should be a numeric value.
rows
This is the UI option for Online Signup Page. Width value should be 1-9 rows and should be a numeric value.

Input Type : Number

min
Minimum number value. Min value should be numerical over 0.
max
Maximum number value. Max value should be numerical under 9,999,999.
default
Default number value.
Request Example: Text Field Case
POST http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}

{
  "required" : 1,
  "options" : 
  {
    "width" : 100
  }
}
Request Example: Radio Button Case
POST http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}

{
  "required" : 1,
  "options" : 
  { 
    "values" :
    [
      "Jaguar", "BMW", "KIA"
    ]
  }
}
Request Example: Drop-down List Case
POST http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}

{
  "required" : 2,
  "options" : 
  { 
    "values" :
    [
      "Jaguar", "BMW", "KIA"
    ]
  }
}
Request Example: Date & Time Case
POST http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}

{
  "required" : 1,
  "options" : 
  { 
    "time" : 1
  }
}
Request Example: Text Area Case
POST http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}

{
  "required" : 1,
  "options" : 
  { 
    "width" : 200,
    "rows" : 5
  }
}
Request Example: Number Case
POST http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}

{
  "required" : 2,
  "options" : 
  { 
    "min" : 17,
    "max" : 100,
    "default" : 20 
  }
}
Response Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP
DELETE Custom Data Field

Permanently remove a custom data field.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:
DELETE http://api.trumpia.com/rest/v1/{user_name}/customdata/{customdata_id}
Request Example:
{
  "request_id" : "1234561234567asdf123"
}
TOP

Number Identity

Look up the carrier of an existing mobile number.

GET /rest/v1/{user_name}/number/identity/{number}
GET Number Identity

Look up the carrier of an existing mobile number. There will be a 1 credit charge for each mobile number lookup. You may also check for supported carriers on the Supported Carriers List.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:

{number} should include country code. For example, 12003004000.

GET http://api.trumpia.com/rest/v1/{user_name}/number/identity/{number}
Response Example:
{
  "carrier_id" : 379,
  "carrier_name" : "AT&T"
}
Response Example: Inactive Number
{
  "carrier_id" : -1,
  "carrier_name" : ""
}
TOP

Report

Report resource provides status report of a request.

GET /rest/v1/{user_name}/report/{request_id}
GET Status Report

Retrieve the status of a request by providing the request ID. A successfully processed request will return the results of the request. If the request is currently being processed or has failed, a message indicating so will be returned.

Sample Codes
Header Parameters

To send a request, the developer must include X-Apikey and content-type parameters in the header.

Header Example:
X-Apikey: 12345aaaaa67890aaaaa
Content-Type: application/json
Request Example:
GET http://api.trumpia.com/rest/v1/{user_name}/report/{request_id}
Response Example:
{
  "request_id" : "1234561234567asdf123",
  "list_id" : "987987987980"
}
TOP
PUSH Notification Inbound Message System Status Code