Maximum 960 characters.Īllows you to schedule message delivery. Separate multiple recipients with a comma (,) where applicable. Recipient Mobile Number in international format (with leading + and country code). If you need to send to more than 1000 simultaneous recipients at a time, try our REST V3 API which can send up to 20000 messages with a single api call. This is the simpler method to use, where the user can send the message just by entering the required information into the url. The GET method uses a query string to send data using the URL. Ideal for less than 100 simultaneous recipients in each API call. POST Variables: method=http&username=xxxx&key=xxxx&to=xxxx,yyyy,zzzz&message=xxxx Payload will be send in posted form variables rather than in the url. Post the message you want to send and all the numbers you want the message to be sent to. Ideal for up to 1000 simultaneous recipients in each API call. There are two options for sending SMS depending on ease of use and the volume you wish to send. header "Content-Type: application/x-www-form-urlencoded" \ This endpoint requires authentication, more info. You can find this in your account area under 'API Credentials' at the top of the screen. header "Content-Type: application/x-www-form-urlencoded" \ '' header "Authorization: Basic YXBpLXVzZXJuYW1lOmFwaS1wYXNzd29yZA=" \ This won't use any of your credit.Ī delivery report won't be generated when using a test number. A success response will be returned.Ī message added to queue 'Success' response will be returned. No messages will be sent, and your account won't be charged. The following numbers can be used when testing. Note: you will need to create a free account to test other scenarios. These API credentials can be used to test specific scenarios. Note: a delivery report won't be generated when using a test number. You can poll our server and retrieve delivery reports at a time that suits you. The temporary status codes can update at any time. Either 'Delivered' or 'Undelivered'.ĭelivery status code. Returned when originally sending the message.ĭelivery status. You can poll our server and retrieve new Messages at a time that suits you. The API username used to send the original message. Original mobile number (sender ID) that the SMS was sent from.Ī custom string used when sending the original message. Returned when originally sending the message. Recipient Mobile Number that sent the reply message. The following parameters will be POSTED to the URL specified. Then click on the Messaging Settings option.Click on your profile on the top right.If you prefer, we can push message replies to your server as they arrive with us. Push - POST the reply to your website or application. Send the reply as an SMS to a nominated mobile number. Send the reply as an email to the original user who sent the message. Send the reply as an email to a nominated email address. There are 5 options for handling message replies: To ensure privacy, we recommend you use HTTPS for all API requests. Your Username or Unique Key is incorrect. You will need to purchase more message credits. You have reached the end of your message credits. Please ensure Sender ID is no longer than 11 characters (if alphanumeric), and contains no spaces. Identical message already sent to this recipient. The destination mobile number is invalid. Please ensure that your Username and Unique Key are supplied in your request. Not enough information has been supplied for authentication. The API will always respond with a 200 OK HTTP status code. Your credentials should be used in the URL or the post body. Simply import our collection and create an environment with username and password variables to get started.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |