SMS API TESTER 
                

End-point URL

https://api.veevotech.com/v3/sendsms



The parameters defined are acceptable via GET, POST or JSON Body  

            

                

GET Sample Request:
    
You can use below mentioned URL to raise a new request, just put relevant 
values in respective fields.
    
                

https://api.veevotech.com/v3/sendsms?hash=API_KEY_HERE&receivernum= 
+923xxxxxxxxx&sendernum=Default&textmessage=HelloWorld
                

                
            
    
            

POST Request JSON Body:
                
Here is JSON Body that can be sent on the above end-point in-case of 
a POST request.
           
    

{
    "apikey": " API_KEY_HERE ",
    "receivernum": "+923001234567",
    "sendernum": "Default",
    "textmessage": "Hello, this is test SMS"
}
    

    
                        
    
                            

The parameters & its description is as follows,

You can send a POST request or GET request, in-case of POST request you need to send above parameters in JSON Body Request, better for handling special characters in SMS body.

            

GET Request Sample URL

You can use below mentioned URL to raise a new request, just put relevant 
values in respective fields.

            

https://api.veevotech.com/v3/sendsms?hash=API_KEY_HERE&receivernum=
+923xxxxxxxxx&sendernum=VT-vOTP&textmessage=Your verification code 1234

            
        

        

Response Parameters
            
You can expect below mentioned parameters in response from API 
endpoint /sendsms, the response is always in JSON format and remains 
the same in-case of SMS or Voice OTP.
Here is a sample JSON response:
       

{
    "STATUS":"SUCCESSFUL",
    "MESSAGE_ID":"4d6a6b31",
    "COUNTRY_SUPPORTED":"TRUE",
    "COUNTRY_CODE":92,
    "COUNTRY_ISO":"PK",
    "NETWORK_NAME":"Mobilink-PK",
    "RECEIVER_NUMBER":"+923001234567",
    "ERROR_FILTER":"",
    "ERROR_CODE":"",
    "ERROR_DESCRIPTION":"",
    "CHARGED_BALANCE":0
}




                    

                        

        

End-point URL
                                
            

https://api.veevotech.com/v3/sendcall                
            
The parameters defined are acceptable via GET, POST or JSON Body  

        
            

GET Request Sample URL

You can use below mentioned URL to raise a new request, just put relevant 
values in respective fields.

            

http://api.veevotech.com/v3/sendcall?apikey=API_KEY_HERE&receivernum=
+923XXXXXXXXX&callerid=Default&recording=10000&max_voice_repeat=
2&max_call_attempts=3&call_template=2&call_parameters={"var1":"1234"}

            
        

        

POST JSON Request Sample Body
            
Here is JSON Body that can be sent on the above end-point in-case of 
a POST request.
       

{
    "apikey": " API_KEY_HERE ",
    "receivernum": "+923001234567",
    "callerid": "Default",
    "recording": 10001,
    "max_voice_repeat": 2,
    "max_call_attempts": 3,
    "call_template": 2,
    "call_parameters":
    {
        "var1":"1234"
    }
}




                    

                        

Response parameters are the same as per Section 1.3 of /sendsms end-point however the only difference is below parameters:

CALL_ID instead MESSAGE_ID which carries placed Call ID.

                
    
            


    

{
    "ACCOUNT_ID": Customer API/Account ID,
    "BILLING_ID": Customer Billing ID,
    "RECEIPENT": Message/Call Receiver number,
    "SENDER_ID": Message/Call SenderCaller ID,
    "MESSAGE_ID": Message Reference ID (returned by the system at the 
                   time of submission). It carries SMS, call, or WhatsApp earlier submitted 
                   request ID as per the medium. In case the medium is SMS, then the message ID 
                   would be the ID of the SMS, and so on.,
    "MEDIUM": Medium on which the message is sent [SMS, VOICE, WHATSAPP],
    "TIME": DDMMYYHHMMSS,
    “CALL_ID”: 83922. It would be the id which our send call api has returned 
               to user for easier tracking, so the user is able to align/connect the 
               received webhook info with the call he has placed earlier in his own app.,
    "CALL_STATUS": In-case of voice call following statuses can be
                   expected:
                  [RINGING, ANSWERED, BUSY, REJECTED, UNANSWERED, ENDED, DISCONNECTED, FAILED, 
                  KEY_PRESSED],
    "CALL_DTMF": The webhook event is activated when a user receives a call and presses a key, 
                 providing information on the key pressed and enabling customers to create  
                 interactive applications, such as surveys, based on user responses.  
                 When the CALL_STATUS key is pressed, value will then be recieved in CALL_DTMF
    "DELIVERY_STATUS": As per SMPP Standards, SMS DLR status is issued
                      accordingly as per
                      following:
                      [ENROUTE, DELIVRD, EXPIRED, DELETED, UNDELIV, ACCEPTD, UNKNOWN,
                      REJECTD],
    "DLR_SMS": As per SMPP Standards, DLR SMS body is passed here,
              incase you want to process the DLR SMS body.
}
    
    
    
    This structured JSON data enables seamless extraction and,
    interpretation of critical information regarding 
    message delivery. Implementing the Callback webhook ensures timely
    updates and insights into the status 
    of your messages/voice calls. 
    You can set your webhook URL within your self-service portal or can
    contact VT Support
    
    Here is a sample webhook URL & the data that is sent for more deeper
    understanding.
    
    Sample Webhook URL
    
    

    https://data.mydomain.com/get_dlr_status
    
    
    Sample Data:
    
    

    {
        "ACCOUNT_ID": 7463,
        "BILLING_ID": 1079483,
        "RECEIPENT": "+923001234567",
        "SENDER_ID": "8333",
        "MESSAGE_ID": "4e7a45354e7a6735",
        "MEDIUM": "SMS",
        "TIME": "281123041233",
        "CALL_ID": 38473,
        "CALL_STATUS": “ANSWERED”,
        "DELIVERY_STATUS": “DELIVRD”,
        "DLR_SMS": " id:103708458 sub:001 dlvrd:001 submit date:
        2811230412 done date:
        2811230412 stat:DELIVRD err:000 text: ”
    }
           
        
    
                        
    
                            

End-point URL

       
https://wa-api.veevotech.com/wa/v1/send_message
   

        

Body Parameters

    


{
    "STATUS": "SUCCESSFUL",
    "ERROR_CODE": "",
    "OTP_CODE": 1234,
    "MESSAGE": "Your call has been scheduled 
    and soon will be processed!"
}


{
    "to": "reciever_number",
    "type": "template",
    "message_ref": "",
    "template_id": 00,
    "mediaUrl":
   ["https://example.com/media/image.jpg"],
    "templateVariables": ["variable1", "variable2"],
    "priority": 1
} 


{
    "to": "reciever_number",
    "type": "document",
    "document": { 
    "id": "media_id",
    "caption" : "example caption",
    "filename" : "example.extension"
    }
} 


{
    "to": "reciever_number",
    "type": "image",
    "image": { 
    "id": "media_id",
    "link": "link",
    "caption" : "example caption"
    }
} 


{
    "to": "reciever_number",
    "type": "audio",
    "audio": { 
    "id": "media_id",
    "link": "link",
    "caption" : "example caption"
    }
} 


{
    "to": "reciever_number",
    "type": "video",
    "video": { 
    "id": "media_id",
    "link": "link",
    "caption" : "example caption"
    }
} 

   
   
   
   


        

    



    Request Parameters

    
       https://wa-api.veevotech.com/wa/media


    “https://elephant.veevotech.com/files/4f4451334e
    673d3d/10_f2b0d8c9e287c21.jpg"

    



    Template Sync Endpoint

    
   https://wa-api.veevotech.com/wa/sync