Sandbox environment for API testing

TextPower provides a "sandbox" environment for developers and partners to use for testing of APIs.  

You can use any API call into our system and it will respond appropriately.  The only difference is that messages will not be sent.  So you can use it to test, for example, the SendSMS call, the ManageOptin call or whatever.  The ManageOptin call as an example will allow you to opt numbers into and out of the sandbox keyword.  The SendSMS call will allow you to test sending a message; you'll get back the proper payload but the message won't be sent. 

Make your test calls using these credentials:

ID: Sandbox-APIonly

Password: tdqSL0HV2FOH$BPNxJ4B

Campaign: sandbox

Keyword: sandbox

Make the calls to our JSON endpoint: https://secure.textpower.com/TPIServices/BasicJSONV4API

Here is an example of our SendSMS API call using this sandbox environment:

{
    "method": "SendSMS",
    "msgcredentials": {
        "UID": "Sandbox-APIonly",
        "PWD": "tdqSL0HV2FOH$BPNxJ4B",
        "Campaign": "sandbox",
        "Keyword": "sandbox"
    },
    "CellNumber": "8182980800",
    "Message": "Testing API call 'SendSMS' to sandbox - will not send",
    "ForceOptIn": true,
    "DelaySend": false,
    "SendTime": "",
    "Queued": false,
    "LangEncoding": 0,
    "IsMultiPartMsg": false
}

 

Here's the payload:

 

{
    "SMSQueued": {
        "Customer": "#InternalTest",
        "MessageStatus": {
            "TimeStamp": "5/24/2021 4:55:17 PM",
            "SendResult": {
                "@SeqNum": "0",
                "QueueID": "11157783",
                "CellNumber": "8182980800",
                "Carrier": "31003",
                "TimeStamp": "5/24/2021 4:55:17 PM",
                "Status": "Queued"
            }
        }
    }
}

 

The payload indicates a successful acceptance and queueing.  When checking logs entries to the test number will show a blank entry in the "TextPower to Carrier" field and of course an "NA" in the Reason Code and "Carrier to Handset" fields (because the message never got to the aggregator - see the attached screenshot).  Of course, no messages all be received because none are sent.  

 

Users can test with this configuration as much as they want; opt-ins will be limited to the one keyword shown above and the message won't ever get sent.  Nightly every opt-in will be cleared out so that anyone who tests it the next day will have a clean opt-in environment to start with.