Menu

WeText SMS API Guide Version 3.0


Contents

  1. Features
  2. Technical Support
  3. Pricing
  4. Getting started
  5. Calling the API
  6. Legal

Key features of the SMS API are as follows:

  • HTTP POST based API
  • Response in JSON
  • Silent API allows you to preserve your brand and integrates with any technology platform which supports HTTP POST and JSON
  • SSL (HTTPS) encryption is available
  • Two-way communication
  • Ability to deliver messages in over 140 countries
  • Not limited to 160 characters text messages which saves a lot of money on per message transaction fees. Longer messages will appear as one large text bubble on most new phones. On some phones, message may be split in multiple 160 character sequential text bubbles
  • Authentication based on IP and client code
  • Incoming replies can be forwarded to an email address, mobile device and/or a website
  • Names can be associated with incoming replies
  • Best-in-the-industry performance and redundancy offered by having a pool of numbers serving outgoing and incoming messages queues. This methodology is used by Google and many other fortune 500 companies

GETTING TECHNICAL SUPPORT

You may contact technical support using following methods:

  • Free email support, subject to terms and conditions of Privi, LLC Privi:support@goprivi.com or WeText:support@wetext.co
  • Phone support (must have support subscription)

Privi: 66924-PRIVI (669.247.7484) or WeText: 732-9-WETEXT (732-993-8398)

  • By visiting our websites GoPrivi.com or www.WeText.co

The SMS API is subject to following charges:

  • One time activation fee
  • Monthly recurring fee based on number of messages sent/received

Latest pricing can be obtained either on our websites or by contacting support/sales.

GETTING STARTED

Following prerequisites must be met before you start testing with the SMS API:

  • Must have a valid client_code. Please contact technical support to obtain one for your company. The client_code is your authentication key and is required in conjunction with the IP address of your server for proper authentication
  • IP address of each server accessing the API must be added to the allowed list. Please contact technical support and provide your IPs to be added to the allowed list

CALLING THE API

Following is an example of how the HTTP POST URL  is constructed to call the SMS API:

PARAMETER REQUIRED DESCRIPTION
Number Yes US: 10 numeric digits. International see here: http://wetext.co/wp

content/uploads/2015/11/WeText_Carriers.pdf

Message Yes Text message body

URLs can be included in the body. Shorter URLs are better.  Include URLs in the first 160 characters to avoid splitting them into two text messages on very old phones. Most new phones will show long text messages as one big text bubble

Client_code Yes Required for authentication

Obtain from technical support

 

METHOD URL
Post http://wetext.co/api/sms_api.php?number=555333

5353&message=Test&client_code=YourCode&reply_email=Incoming Reply@YourDomain.com&reply_cell=3335553535&reply_post_url= http://www.example.com/yourfile.php&recipient_name=John Doe

Above POST can be performed from any language which supports HTTP POST.

json   

response

{“status”:”Successful”,”number”:”5553335353”,”message”:”Test”,

”client_code”:”YourCode”,”reply_email”:” IncomingReply@YourDomain.com “,”reply_cell”:”3335553535”,”reply_post_url”:”http:\/\/ www.example. com/yourfile.php “,”recipient_name”:”John Doe”}

First field in JSON response is ‘status’ which will contain ‘Successful’ if the  API call was successful or will contain an error message. The rest of the  JSON response will simply echo back the parameters passed via POST.

 

CALLING THE API (continued)

HTTP POST Parameters

PARAMETER REQUIRED DESCRIPTION
reply_email No •             Provide a valid email to which the incoming text reply will be forwarded

•             To disable reply forwarding to email, do not include the reply_email parameter in the API call while sending the outgoing text message

reply_cell

 

No •             Provide a valid cell phone number to which the    incoming text reply will be forwarded

•             To disable reply forwarding to cell, do not include the reply_cell parameter in the API call while sending the outgoing message

reply_post_url No •         Provide a valid URL to which the incoming text reply will be posted via HTTP POST

•         To disable reply forwarding to URL, do not include the reply_post_url parameter in the API call while sending the outgoing message

 

Following parameters will be sent via HTTP POST:  received_timestamp – Timestamp indicating when the incoming text message was received by our server in the format:

‘08/18/2016 11:08:33 AM’  sender – Cell phone number from which the incoming text message was received

message – Body of the incoming text message  reply_email – Email address to which this incoming text message will be forwarded reply_cell – Cell phone number to which this incoming text message will be forwarded

reply_post_url – URL to which this incoming text message is being posted via HTTP POST

Sender_name – Name of the sender, if provided while the outgoing message was sent.

recipient_name No Provide the name of the recipient to which the message is being sent. This name will be used in reply forwarding notifications if incoming response is received

 

LEGAL INFORMATION

It is illegal in USA and many other countries to send Text/MMS messages to individuals who have not opted in previously. Please do not use the SMS API to send messages without prior consent of the recipient. As per Privi, LLC terms and conditions, while using the SMS API, you are solely responsible for maintaining opt in procedure as well as records and are liable for any violations.

 

Support Plans and Pricing

 

  SILVER GOLD PLATINUM Pay Per Incident
Price FREE $99 USD/Month $299 USD/Month $149

USD/Incident

Response Time Within 5 business days Within 1-2 business days Within 4 hours Within 4 hours
Support via email  Yes Yes Yes Yes
Support via phone No Yes Yes Yes
Support via text No No Yes Yes
Support via remote dial in No No Yes Yes

 

Share Via:

Leave a Reply

Your email address will not be published. Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.

Already a customer? LOGIN HERE

Help with Sign up?

Contact us at 732-9-WETEXT (732-993-8398) or
support@wetext.co


Reach your audience anywhere, saving time and money.

Send this demonstration to your mobile. A text message will be sent to your cell phone to begin the live demo sequence.

  • US: 10 numeric digits. International see here.
 
  1. Verify your info
  2. Pick your Keyword
  3. Enter WeText Trial Verification Code
  4. Referral Code
  5. Let's Go
  • Verify your info

  • Pick your Keyword



    Select a keyword that is unique to your business. Keep it short so it's easy for your customers.

    For example:
    1) Amore Pizza - Keyword should be Amore
    2)Zumba with JoAnne - Keyword should be ZumbaJo
    Keyword
  • Enter WeText Trial Verification Code

    • Please enter the WeText Trial Verification Code we sent to your mobile.
    • Did not receive the code? Click the RESEND CODE button below.
    •  
    • Having trouble? Please click the chat button or email support@wetext.co.
  • Referral Code



    Did someone refer you to WeText and give you a Referral Code? If so, input it now or click next to move on. Please do not enter your WeText Trial Verification Code we sent to your mobile.
  • Let's Go

    Your trial account has been created. We are excited to have you working with our platform. You will be WeTexting in no time! Now let's get you set up!
    Let's Go!
    (set up your first campaign now.)

Set New Password

To Register Now Select one of the following:

Help with SIGN UP?

Contact us at 732-9-WETEXT (732-993-8398) or
support@wetext.co

SIGN UP

  • Enter Your Keyword: Please enter a new keyword that you would like to register. Your keyword should be maximum of 12 characters long. It should only contain alphanumeric(numbers and letters) characters. It should be one word and should not contain any spaces or special characters. We recommend making it short because short keywords are easier to type while triggering alerts/messages from your cell phone. The keyword should also be descriptive and can reflect the name of your organization such as "mtv", "mit", "wetext"...etc.
  • When you subscribe, alerts/messages are sent to your mobile device via standard text messaging (SMS), multimedia messaging services(MMS) or your internet connection. Standard Carrier Rates Apply. By clicking Submit you agree to our Terms and Conditions.