Contacts   0039 02 40 70 72 40
EN IT flag-down
FREE SIGN UP         LOGIN

Documentation

Simple SMS APIs allow you to integrate Skebby's powerful SMS gateway into your application or web server, quickly and simply. In the following paragraphs we'll show you how to send and receive text messages using various different programming languages. If you need any assistance in getting our APIs working, we'll be happy to help.



Send SMS


Send Classic SMS

Sends an SMS Classic and replies with remaining SMS balance

  • Url for HTTP requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/http.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/http.php

    Parameters has to be sent with POST method, in the standard urlencode. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms_classic
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in an Array form e.g.:

    recipients[]=393334455666&recipients[]=393334455667

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    The recipients string, in a multidimensional Array form, will be:
    recipients[0][recipient]=393471234567&recipients[0][nome]=Mario&recipients[1][recipient]=393477654321&recipients[1][nome]=Marco

    String text Text of the message, maximum length 1530 characters or "10 SMS" concatenated in one message. To view messages' count go on Messages' count method for long traditional SMS

    Optional parameters:
    Parameter Description
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666

    WARNING: it's necessary to specify the number in international format, otherwise the SMS recipient might be unable to answer to the message.
    String sender_string* Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String charset See note on use of charset
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822
    String encoding_scheme To use accented or special characters commonly used in the following languages: Arabic, French, Chinese, Korean, Japanese, Slavic and Spanish
    Values accepted:
    • normal (7 bit, default)
    • UCS2

    Text of the message, maximum lenght 670 characters or 10 SMS concatenated in one message. To view message' count go on Messages' count method for long UCS2 SMS

    Integer validity_period You can specify for how many minutes (or hours) the operator must retry to send the SMS in case of phone turned off or unreachable.
    Expressed in minutes, integer number (minimum value 5 minutes), default 2days = 2880(60*48)**


    Example of HTTP body for sending multiple Classic SMS with personalised alphanumeric sender ID:

    Messages' count method to send long SMS
    Traditional SMS:
    The price of the message will be counted every 153 chars, except the first SMS that will be of 160 chars, up to 1530 chars or 10 SMS concatenated.

    Chars Number of SMS charged
    Caratteri Numero di SMS addebitati
    0-160 1
    161-306 2
    307-459 3
    460-612 4
    613-765 5
    766-918 6
    919-1071 7
    1072-1224 8
    1225-1377 9
    1378-1530 10

    Some chars count double:
    [ Open square bracket
    \ Backslash
    ] Closed square bracket
    ^ Caret
    { Open curly brackets
    | Vertical bar
    } Closed curly brackets
    ~ Tilde
    Euro symbol

    SMS UCS2:
    The price of the message will be counted every 67 chars, except the first SMS that will be of 70 chars, up to 670 chars or 10 SMS concatenated

    Chars Number of SMS charged
    0-70 1
    71-134 2
    135-201 3
    202-268 4
    269-335 5
    336-402 6
    403-469 7
    470-536 8
    537-603 9
    604-670 10

    Send bulk SMS
    To send bulk SMS and optimise delivery times, we recommend you use "single request sending", which gives you the option of customising your message text if necessary by using "Dynamic variables", documentation on which is available here by clicking on "Customize text for every recipient". This method allows you to send a single request to the server and send customised messages to each of your contacts, receiving a delivery report for every SMS you send, as specified here. For anyone needing to send large numbers of bulk SMS, "Single request bulk SMS sending" is much faster and more efficient than sending one text at a time using a sequence of "individual requests". The latter method requires much more time to manage the message dispatch. Here’s an example: to send 50,000 text messages through bulk sending from a basic account with a capacity of 10 SMS per second, consecutive requests would have to be sent from the SMS server to the Skebby gateway for 83 minutes, whereas a single send requires a single request lasting under a second; after which, the Skebby gateway will manage the request and complete it in just a few minutes.

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
    **The default value of the Validity Period (VP) is 48 hours, which is the standard uses from the majority of the mobile operator in the world. Anyhow, it is possible to specify for how many hours the operator must retry to send the SMS in case of mobile phone turned off or unreachable at your choice within maximum 48 hours.

  • Url for REST requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/rest.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/rest.php

    Parameters of REST requests has to be sent with POST method. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory Parameters:
    Parameter Description
    String method send_sms_classic
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in JSON Array form e.g.:

    recipients = [ "443334455666" , "443334455667" ];

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    The recipients string, in JSON Array form, will be:
    ?recipients=[{recipient:'393471234567',nome:'Mario'},{recipient:'393477654321',nome:'Marco'}]

    String text Text of the message, maximum length 1530 characters or "10 SMS" concatenated in one message. To view messages' count go on Messages' count method for long traditional SMS

    Optional parameters:
    Parameter Description
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string* Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String charset See note sull'utilizzo del charset
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822
    String encoding_scheme To use characters that special characters (i.e. Arabic, French, Chinese, Korean, Japanese, Slavic and Spanish)
    Values accepted:
    • normal (7 bit, default)
    • UCS2

    Text of the message, maximum lenght 670 characters or 10 SMS concatenated in one message. To view message' count go on Messages' count method for long UCS2 SMS

    Integer validity_period You can specify for how many minutes (or hours) the operator must retry to send the SMS in case of phone turned off or unreachable.
    Expressed in minutes, integer number (minimum value 5 minutes), default 2days = 2880(60*48)**


    Example of REST body for sending multiple Classic SMS with customized numeric sender ID:

    Messages' count method to send long SMS
    Traditional SMS:
    The price of the message will be counted every 153 chars, except the first SMS that will be of 160 chars, up to 1560 chars or 10 SMS concatenated.

    Chars Number of SMS charged
    0-160 1
    161-306 2
    307-459 3
    460-612 4
    613-765 5
    766-918 6
    919-1071 7
    1072-1224 8
    1225-1377 9
    1378-1530 10

    Some chars count double:
    [ Open square bracket
    \ Backslash
    ] Closed square bracket
    ^ Caret
    { Open curly brackets
    | Vertical bar
    } Closed curly brackets
    ~ Tilde
    Euro symbol

    SMS UCS2:
    The price of the message will be counted every 67 chars, except the first SMS that will be of 70 chars, up to 670 chars or 10 SMS concatenated

    Chars Number of SMS charged
    0-70 1
    71-134 2
    135-201 3
    202-268 4
    269-335 5
    336-402 6
    403-469 7
    470-536 8
    537-603 9
    604-670 10

    Send bulk SMS
    To send bulk SMS and optimise delivery times, we recommend you use "single request sending", which gives you the option of customising your message text if necessary by using "Dynamic variables", documentation on which is available here by clicking on "Customize text for every recipient". This method allows you to send a single request to the server and send customised messages to each of your contacts, receiving a delivery report for every SMS you send, as specified here. For anyone needing to send large numbers of bulk SMS, "Single request bulk SMS sending" is much faster and more efficient than sending one text at a time using a sequence of "individual requests". The latter method requires much more time to manage the message dispatch. Here’s an example: to send 50,000 text messages through bulk sending from a basic account with a capacity of 10 SMS per second, consecutive requests would have to be sent from the SMS server to the Skebby gateway for 83 minutes, whereas a single send requires a single request lasting under a second; after which, the Skebby gateway will manage the request and complete it in just a few minutes.

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
    **The default value of the Validity Period (VP) is 48 hours, which is the standard uses from the majority of the mobile operator in the world. Anyhow, it is possible to specify for how many hours the operator must retry to send the SMS in case of mobile phone turned off or unreachable at your choice within maximum 48 hours.

  • File wsdl with the description of the methods is available at this address:

    http://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl

    Compulsory parameters:
    Parameter Description
    String username Username you used to sign up
    String password Password you used to sign up
    Recipient[] recipients Array of recipients, in international format without + or 00

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    Recipients must be sent as an Array of Recipient objects, each containing the recipient number and possibly an Array of dynamic variables.

    String text Text of the message, maximum length 1530 characters or "10 SMS" concatenated in one message. To view messages' count go on Messages' count method for long traditional SMS

    Optional parameters:
    Parameter Description
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string* Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822
    String encoding_scheme To use characters that do not belong to Latin alphabet (i.e. Arabic, Chinese, Korean, Japanese, Cyrillic, etc ...)
    Values accepted:
    • normal (7 bit, default)
    • UCS2

    Text of the message, maximum lenght 670 characters or 10 SMS concatenated in one message. To view message' count go on Messages' count method for long UCS2 SMS

    Integer validity_period You can specify for how many minutes (or hours) the operator must retry to send the SMS in case of phone turned off or unreachable.
    Expressed in minutes, integer number (minimum value 5 minutes), default 2days = 2880(60*48)**

    Messages' count method to send long SMS
    Traditional SMS:
    The price of the message will be counted every 153 chars, except the first SMS that will be of 160 chars, up to 1530 chars or 10 SMS concatenated.

    Chars Number of SMS charged
    0-160 1
    161-306 2
    307-459 3
    460-612 4
    613-765 5
    766-918 6
    919-1071 7
    1072-1224 8
    1225-1377 9
    1378-1530 10

    Some chars count double:
    [ Open square bracket
    \ Backslash
    ] Closed square bracket
    ^ Caret
    { Open curly brackets
    | Vertical bar
    } Closed curly brackets
    ~ Tilde
    Euro symbol

    SMS UCS2:
    The price of the message will be counted every 67 chars, except the first SMS that will be of 70 chars, up to 670 chars or 10 SMS concatenated

    Chars Number of SMS charged
    0-70 1
    71-134 2
    135-201 3
    202-268 4
    269-335 5
    336-402 6
    403-469 7
    470-536 8
    537-603 9
    604-670 10

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
  • How to use SMTP protocol to send SMS Classic from client/server email too
    To send SMS with SMTP protocol you need to enable the service by indicating which email account you want to use for sending. To set it up, go to Skebby.com > Sign in > Settings > Company name. If you want to send SMS from another account email, you will just have to add it. You can add as many accounts as you like.
    Parameter
    Parameter Description
    SMS Recipient The recipient of the SMS must be entered in the "A" or "CC" field using the following format: MOBILENUMBER@classic.skebby.com. The mobile number must be entered in international format, customers can choose from the example formats shown below:
    0039320XXXXXXX@classic.skebby.com
    +39320XXXXXXX@classic.skebby.com
    39320XXXXXXX@classic.skebby.com
    It is possible to send bulk messages up to 50 email/SMS simultaneously. If you send more than 50 email with this method the service will be suspended.

    Example: 00393334455666@classic.skebby.com
    Multiple recipients / Bulk sending To send up to 100 email/SMS you can send an SMS by entering each additional recipient to the "CC" field. To send greater than 100 and up to 50,000 email/SMS add the recipients in the standard format in the body of the email after the ## character that indicates the end of the text to be sent. You don’t need to enter spaces or any other chars between one recipient and the following.
    Sending to groups You can send an SMS to a group previously saved on Skebby.com > Login > Contacts > Groups by entering it in the "To" or "CC" field of the email using the following format:
    GROUPNAME@classic.skebby.com
    Example: colleagues@classic.skebby.com
    The group name must be one word, the same as the one saved on Skebby.com and contain at least one alphabetic char.
    To send SMS to the default group:
    • "Favorites" contacts send an email to favorites@classic.skebby.com
    • "Mobile address book" contacts send an email to mobileaddressbook@classic.skebby.com
    • All contacts send an email to allcontacts@classic.skebby.com
    SMS Sender All SMS will be sent from the default Sender ID set up on your Skebby account. You can customized the sender at every dispatch with an alphanumeric string of 11 characters maximum lenght in the Subject field of the email, supported characters [a-zA-Z0-9 .]
    Message text The message text must be written within the body of the email where you'd usually write the text of your email and the maximum lenght is 1530 characters ("10"). If you enter a text longer than 1530 characters the message will not be sent and you will be alert with an email. If the body of the email is empty, the email will be sent but the SMS will not arrive (no message charged).
    End of SMS The characters ## indicates the end of the text to be sent and it marks the end of the SMS. It must always be included. Any text after ## will not be sent.
    PIN Authentication You can request PIN authentication when sending SMS to email for greater security, by setting it up in your Skebby account settings. In order to send SMS by email the sender must include an address among the recipients, e.g.:. yourpin123@pin.skebby.com, where "yourpin123" corresponds to an alphanumeric security code (minimum 6 characters), which is indicated by the user in the Private Area i.e. Skebby.com > Sign in > Settings > Company name. If you choose PIN authentication, to send an SMS from any email address you've registered it will be compulsory to enter the email address with PIN as one of the recipients, otherwise the message will not be sent.

Send Classic + SMS (with delivery report)

Sends an SMS Classic with Delivery Report and replies with remaining SMS balance and delivery id code.

  • Url for HTTP requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/http.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/http.php

    Parameters has to be sent with POST method, in the standard urlencode. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms_classic_report
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in an Array form e.g.:

    recipients[]=393334455666&recipients[]=393334455667

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    The recipients string, in a multidimensional Array form, will be:
    recipients[0][recipient]=393471234567&recipients[0][nome]=Mario&recipients[1][recipient]=393477654321&recipients[1][nome]=Marco

    String text Text of the message, maximum length 1530 characters or "10 SMS" concatenated in one message. To view messages' count go on Messages' count method for long traditional SMS

    Optional parameters:
    Parameter Description
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666

    WARNING: it's necessary to specify the number in international format, otherwise the SMS recipient might be unable to answer to the message.
    String sender_string* Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String charset See note on use of charset
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822
    String encoding_scheme To use accented or special characters commonly used in the following languages: Arabic, French, Chinese, Korean, Japanese, Slavic and Spanish
    Values accepted:
    • normal (7 bit, default)
    • UCS2

    Text of the message, maximum lenght 670 characters or 10 SMS concatenated in one message. To view messages' count go on Messages' count method for long UCS2 SMS

    Integer validity_period You can specify for how many minutes (or hours) the operator must retry to send the SMS in case of phone turned off or unreachable.
    Expressed in minutes, integer number (minimum value 5 minutes), default 2days = 2880(60*48)**
    Varchar(20) user_reference Reference string customizable that will be returned with the delivery report.
    Supported characters: [a-zA-Z0-9-_+:;]

    Example of HTTP body for sending multiple Classic SMS with delivery report with customized numeric sender ID:

    Messages' count method to send long SMS
    Traditional SMS:
    The price of the message will be counted every 153 chars, except the first SMS that will be of 160 chars, up to 1530 chars or 10 SMS concatenated.

    Chars Number of SMS charged
    0-160 1
    161-306 2
    307-459 3
    460-612 4
    613-765 5
    766-918 6
    919-1071 7
    1072-1224 8
    1225-1377 9
    1378-1530 10

    Some chars count double:
    [ Open square bracket
    \ Backslash
    ] Closed square bracket
    ^ Caret
    { Open curly brackets
    | Vertical bar
    } Closed curly brackets
    ~ Tilde
    Euro symbol

    SMS UCS2:
    The price of the message will be counted every 67 chars, except the first SMS that will be of 70 chars, up to 670 chars or 10 SMS concatenated

    Chars Number of SMS charged
    0-70 1
    71-134 2
    135-201 3
    202-268 4
    269-335 5
    336-402 6
    403-469 7
    470-536 8
    537-603 9
    604-670 10

    Send bulk SMS with delivery report for every SMS sent
    To send bulk SMS and optimise delivery times, we recommend you use "single request sending", which gives you the option of reconciling if necessary every delivery report to every message sent. All you need to do is use both the "Sender ID" and "Recipient’s mobile number" fields offered for every report forwarded, which make every delivery report unique. For anyone needing to send large numbers of bulk SMS, "Single request bulk SMS sending" is much faster and more efficient than sending one text at a time using a sequence of "individual requests".

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
    **The default value of the Validity Period (VP) is 48 hours, which is the standard uses from the majority of the mobile operator in the world. Anyhow, it is possible to specify for how many hours the operator must retry to send the SMS in case of mobile phone turned off or unreachable at your choice within maximum 48 hours.

  • Url for REST requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/rest.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/rest.php

    Parameters of REST requests has to be sent with POST method. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms_classic_report
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in JSON Array form e.g.:

    recipients = [ "393334455666" , "393334455667" ];

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    The recipients string, in JSON Array form, will be:
    ?recipients=[{recipient:'393471234567',nome:'Mario'},{recipient:'393477654321',nome:'Marco'}]

    String text Text of the message, maximum length 1530 characters or "10 SMS" concatenated in one message. To view messages' count go on Messages' count method for long traditional SMS

    Optional parameters:
    Parameter Description
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string* Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String charset See note on use of charset
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822
    String encoding_scheme To use characters that do not belong to Latin alphabet (i.e. Arabic, Chinese, Korean, Japanese, Cyrillic, etc ...)
    Values accepted:
    • normal (7 bit, default)
    • UCS2

    Text of the message, maximum lenght 670 characters or 10 SMS concatenated in one message. To view message' count go on Messages' count method for long UCS2 SMS

    Integer validity_period You can specify for how many minutes (or hours) the operator must retry to send the SMS in case of phone turned off or unreachable.
    Expressed in minutes, integer number (minimum value 5 minutes), default 2days = 2880(60*48)**
    Varchar(20) user_reference Reference string customizable that will be returned with the delivery report.
    Supported characters: [a-zA-Z0-9-_+:;]

    Example of REST body for sending multiple Classic SMS with delivery report with customized numeric sender ID:

    Messages' count method to send long SMS
    Traditional SMS:
    The price of the message will be counted every 153 chars, except the first SMS that will be of 160 chars, up to 1530 chars or 10 SMS concatenated.

    0-160 1
    161-306 2
    307-459 3
    460-612 4
    613-765 5
    766-918 6
    919-1071 7
    1072-1224 8
    1225-1377 9
    1378-1530 10

    Some chars count double:
    [ Open square bracket
    \ Backslash
    ] Closed square bracket
    ^ Caret
    { Open curly brackets
    | Vertical bar
    } Closed curly brackets
    ~ Tilde
    Euro symbol

    SMS UCS2:
    The price of the message will be counted every 67 chars, except the first SMS that will be of 70 chars, up to 670 chars or 10 SMS concatenated

    Chars Number of SMS charged
    0-70 1
    71-134 2
    135-201 3
    202-268 4
    269-335 5
    336-402 6
    403-469 7
    470-536 8
    537-603 9
    604-670 10

    Send bulk SMS with delivery report for every SMS sent
    To send bulk SMS and optimise delivery times, we recommend you use "single request sending", which gives you the option of reconciling if necessary every delivery report to every message sent. All you need to do is use both the "Sender ID" and "Recipient’s mobile number" fields offered for every report forwarded, which make every delivery report unique. For anyone needing to send large numbers of bulk SMS, "Single request bulk SMS sending" is much faster and more efficient than sending one text at a time using a sequence of "individual requests".

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
    **The default value of the Validity Period (VP) is 48 hours, which is the standard uses from the majority of the mobile operator in the world. Anyhow, it is possible to specify for how many hours the operator must retry to send the SMS in case of mobile phone turned off or unreachable at your choice within maximum 48 hours.

  • File wsdl with the description of the methods is available at this address:

    http://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl

    Compulsory parameters:
    Parameter Description
    String username Username you used to sign up
    String password Password you used to sign up
    Recipient[] recipients Array of recipients, in international format without + or 00

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    Recipients must be sent as an Array of Recipient objects, each containing the recipient number and possibly an Array of dynamic variables.

    String text Text of the message, maximum length 1530 characters or "10 SMS" concatenated in one message. To view messages' count go on Messages' count method for long traditional SMS

    Optional parameters:
    Parameter Description
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string* Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822
    String encoding_scheme To use characters that do not belong to Latin alphabet (i.e. Arabic, Chinese, Korean, Japanese, Cyrillic, etc ...)
    Values accepted:
    • normal (7 bit, default)
    • UCS2

    Text of the message, maximum lenght 670 characters or 10 SMS concatenated in one message. To view message' count go on Messages' count method for long UCS2 SMS

    Integer validity_period You can specify for how many minutes (or hours) the operator must retry to send the SMS in case of phone turned off or unreachable.
    Expressed in minutes, integer number (minimum value 5 minutes), default 2days = 2880(60*48)**
    Varchar(20) user_reference Reference string customizable that will be returned with the delivery report.
    Supported characters: [a-zA-Z0-9-_+:;]

    Messages' count method to send long SMS
    Traditional SMS:
    Text of the message will be counted every 153 chars, except the first SMS that will be of 160 chars, up to 1530 chars or 10 SMS concatenated.

    Chars Number of SMS charged
    0-160 1
    161-306 2
    307-459 3
    460-612 4
    613-765 5
    766-918 6
    919-1071 7
    1072-1224 8
    1225-1377 9
    1378-1530 10

    Some chars count double:
    [ Open square bracket
    \ Backslash
    ] Closed square bracket
    ^ Caret
    { Open curly brackets
    | Vertical bar
    } Closed curly brackets
    ~ Tilde
    Euro symbol

    SMS UCS2:
    The price of the message will be counted every 67 chars, except the first SMS that will be of 70 chars, up to 670 chars or 10 SMS concatenated

    Chars Number of SMS charged
    0-70 1
    71-134 2
    135-201 3
    202-268 4
    269-335 5
    336-402 6
    403-469 7
    470-536 8
    537-603 9
    604-670 10

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
  • How to use SMTP protocol to send SMS Classic con Notifica from client/server email too
    To send SMS with SMTP protocol you need to enable the service by indicating which email account you want to use for sending. To set it up, go to Skebby.com > Sign in > Settings > Company name. If you want to send SMS from another account email, you will just have to add it. You can add as many accounts as you like.
    Parameter
    Parameter Description
    SMS Recipient The recipient of the SMS must be entered in the "A" or "CC" field using the following format: MOBILENUMBER@classicplus.skebby.com. The mobile number must be entered in international format, customers can choose from the example formats shown below:
    0039320XXXXXXX@classicplus.skebby.com
    +39320XXXXXXX@classicplus.skebby.com
    39320XXXXXXX@classicplus.skebby.com
    It is possible to send bulk messages up to 50 email/SMS simultaneously. If you send more than 50 email with this method the service will be suspended.

    Example: 00393334455666@classicplus.skebby.com
    Multiple recipients / Bulk sending To send up to 100 email/SMS you can send an SMS by entering each additional recipient to the "CC" field. To send greater than 100 and up to 50,000 email/SMS add the recipients in the standard format in the body of the email after the ## character that indicates the end of the text to be sent. You don’t need to enter spaces or any other chars between one recipient and the following.
    Sending to groups You can send an SMS to a group previously saved on Skebby.com > Login > Contacts > Groups by entering it in the "To" or "CC" field of the email using the following format:
    GROUPNAME@classicplus.skebby.com
    Example: colleagues@classicplus.skebby.com
    The group name must be one word, the same as the one saved on Skebby.com and contain at least one alphabetic char.
    To send SMS to the default group:
    • "Favorites" contacts send an email to favorites@classicplus.skebby.com
    • "Mobile address book" contacts send an email to mobileaddressbook@classicplus.skebby.com
    • All contacts send an email to allcontacts@classicplus.skebby.com
    SMS Sender All SMS will be sent from the default Sender ID set up on your Skebby account. You can customized the sender at every dispatch with an alphanumeric string of 11 characters maximum lenght in the Subject field of the email, supported characters [a-zA-Z0-9 .]
    Message text The message text must be written within the body of the email where you'd usually write the text of your email and the maximum lenght is 1530 characters ("10"). If you enter a text longer than 1530 characters the message will not be sent and you will be alert with an email. If the body of the email is empty, the email will be sent but the SMS will not arrive (no message charged).
    End of SMS The characters ## indicates the end of the text to be sent and it marks the end of the SMS. It must always be included. Any text after ## will not be sent.
    PIN Authentication You can request PIN authentication when sending SMS to email for greater security, by setting it up in your Skebby account settings. In order to send SMS by email the sender must include an address among the recipients, e.g.:. yourpin123@pin.skebby.com, where "yourpin123" corresponds to an alphanumeric security code (minimum 6 characters), which is indicated by the user in the Private Area i.e. Skebby.com > Sign in > Settings > Company name. If you choose PIN authentication, to send an SMS from any email address you've registered it will be compulsory to enter the email address with PIN as one of the recipients, otherwise the message will not be sent.

How to receive delivery reports for every Classic + SMS

You can receive the delivery reports if you send SMS Classic+. You can request and get the report in three different ways:
  1. In real time via a call to your server for each SMS sent. To set it up go on Skebby.com > Log in > Settings > Send SMS > Delivery report and set up the sending protocol wanted (GET/POST/REST/SOAP) and the destination URL for the reports. In the moment that the server Skebby calls the indicated URL for the forwarding of the report and the URL is not reachable, the server Skebby will try to return the report every 30 minutes for a maximum of 6 attempts (3 hours maximum from the sending), afterward which the forwarding will be rejected.
  2. You can visualize the delivery report's detail on Skebby web application SMS Messenger by going to Skebby.com > Log in > Reports > SMS traffic and notifications > Traffic history.




  • The parameters sent to the URL specified are:
    Parameter Description
    String skebby_dispatch_id Delivery ID number
    String skebby_message_id ID number of individual SMS
    String recipient Phone number to which the SMS was sent
    String status Status report code (view below for the details)
    String error_code Delivery report detail (view below)
    String user_reference Reference string, it will be returned if specify during the sending of Classic SMS with delivery report
    String skebby_date_time Date of receipt of the report from our systems in the format RFC 2822
    View specification RFC 2822
    String operator_date_time Date of receipt of the report provided by the provider in the format
    View specification RFC 2822


    Example of HTTP body for receiving Classic + SMS report:




  • For SOAP/REST requests, a method called "notify" has to be used with the following items:
    Parameter Description
    String skebby_dispatch_id Delivery ID number
    String skebby_message_id ID number of individual SMS
    String recipient Phone number to which the SMS was sent
    String status Status report code (view below for the details)
    String error_code Delivery report detail (view below)
    String user_reference Reference string, it will be returned if specify during the sending of Classic SMS with report
    String skebby_date_time Date of receipt of the report from our systems in the format RFC 2822
    View specification RFC 2822
    String operator_date_time Date of receipt of the report provided by the provider in the format
    View specification RFC 2822




The following parameters will be returned for the status variable:
Parameter Meaning
DELIVERED Message delivered
EXPIRED Message expired (device off/not reachable)
DELETED Operator network error
UNDELIVERABLE Message undelivered (View below error_code variable)
UNKNOWN Generic error
REJECTD Message rejected from operator


The following parameters will be returned for the error_code variable:
Error code Meaning
101 Generic operator malfunctioning
201 Operator network malfunctioning
202 Message rejected from operator
203 Recipient unreachable (in roaming)
301 Invalid recipient (nonexistent/on portability/not enabled)
302 Wrong number
303 SMS service not enabled
304 Text identified as spam
401 Message expired (device off/not reachable)
501 Device doesn't support SMS
502 Device with memory full

Click here to view response server examples when you send Classic + SMS

How to receive delivery reports for every Classic + SMS

You can receive the delivery reports if you send Classic + SMS. To set it go on Skebby.com > Log in > Settings > Send SMS > Delivery report and set up the sending protocol wanted (GET/POST/REST/SOAP) and the destination URL for the reports.
In the moment that the server Skebby calls the indicated URL for the forwarding of the report and the URL is not reachable, the server Skebby will try to return the report every 30 minutes for a maximum of 6 attempts (3 hours maximum from the sending), afterward which the forwarding will be rejected.
Further more you can visualize the delivery report's detail on Skebby.com > Log in > Reports > SMS traffic and notifications > Traffic history.





  • The parameters sent to the URL specified are:
    Parameter Description
    String smsID Delivery ID number
    String messageID ID number of individual SMS
    String destination Phone number to which the SMS was sent
    String smsStatus Status report code
    Varchar(20) userReference Reference string, it will be returned if specify during the sending
    of Classic SMS with report
    String smscDate Date of receipt of the report provided by the provider in the format RFC 2822.
    View specification RFC 2822


    Example of HTTP body for receiving Classic + SMS report:




  • For SOAP/REST requests, a method called "notify" has to be used with the following items:
    Parameter Description
    String smsID Delivery ID number
    String messageID ID number of individual SMS
    String destination Phone number to which the SMS was sent
    String smsStatus Status report code
    Varchar(20) userReference Reference string, it will be returned if specify during the sending
    of Classic SMS with report
    String smscDate Date of receipt of the report provided by the provider in the format RFC 2822.
    View specification RFC 2822




In both cases, the following codes will be returned for the smsStatus variable:
Code Meaning
0 Reception error
1 Delivered
2 Generic error
3 Inexistent number
4 Recipient unavailable
5 Recipient not enable
6 Network problems
7 Delivery failed
8 Message refused


Request approval of alphanumeric sender

Through this function you can add information related to the alphanumeric senders or Aliases. This is needed only while sending to italian mobile numbers (+39).
More information.


  • Url for HTTP requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/http.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/http.php

    Parameters has to be sent with POST method, in the standard urlencode.

    Compulsory parameters:
    Parameter Description
    String method add_alias
    String username Username you used to sign up
    String password Password you used to sign up
    String alias Alphanumeric sender
    String business_name Business name
    String nation Country (2 characters, uppercase, ISO 3166-1 alpha-2)
    String vat_number Vat
    String taxpayer_number Taxpayer Identification number (same as vat if not available)
    String street Street
    String city City
    String postcode Postal code
    String contact Contact information (email, phone number)

    Optional parameters:
    Parameter Description
    String charset See note on use of charset


    Example of HTTP body for adding an alphanumeric sender:


    Values accepted as alphanumeric sender
    The alphanumeric sender:
    • can be at most 11 characters long (except for the that corresponds to the use of 2 characters);
    • in addition to the common alphanumeric characters, it can contain the following special characters èéùìòà!',.:;?"$£€%()+-=@_#&* and non consecutive spaces;
    • can contain only two quotation marks. The first can not precede a space and the second can not follow a space.


  • Url for REST requests:

    Secure https://gateway.skebby.it/api/send/smseasy/advanced/rest.php

    Parameters of REST requests has to be sent with POST method.

    Compulsory parameters:
    Parameter Description
    String method add_alias
    String username Username you used to sign up
    String password Password you used to sign up
    String alias Alphanumeric sender
    String business_name Business name
    String nation Country (2 characters, uppercase, ISO 3166-1 alpha-2)
    String vat_number Vat
    String taxpayer_number Taxpayer Identification number (same as vat if not available)
    String street Street
    String city City
    String postcode Postal code
    String contact Contact information (email, phone number)

    Optional parameters:
    Parameter Description
    String charset See note on use of charset


    Example of HTTP body for adding an alphanumeric sender:


    Values accepted as alphanumeric sender
    The alphanumeric sender:
    • can be at most 11 characters long (except for the that corresponds to the use of 2 characters);
    • in addition to the common alphanumeric characters, it can contain the following special characters èéùìòà!',.:;?"$£€%()+-=@_#&* and non consecutive spaces;
    • can contain only two quotation marks. The first can not precede a space and the second can not follow a space.


  • File wsdl with the description of the methods is available at this address:

    http://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl

    Compulsory parameters:
    Parameter Description
    String username Username you used to sign up
    String password Password you used to sign up
    String alias Alphanumeric sender
    String business_name Business name
    String nation Country (2 characters, uppercase, ISO 3166-1 alpha-2)
    String vat_number Vat
    String taxpayer_number Taxpayer Identification number (same as vat if not available)
    String street Street
    String city City
    String postcode Postal code
    String contact Contact information (email, phone number)


    Values accepted as alphanumeric sender
    The alphanumeric sender:
    • can be at most 11 characters long (except for the that corresponds to the use of 2 characters);
    • in addition to the common alphanumeric characters, it can contain the following special characters èéùìòà!',.:;?"$£€%()+-=@_#&* and non consecutive spaces;
    • can contain only two quotation marks. The first can not precede a space and the second can not follow a space.



How to receive the approval/rejection notification of alphanumeric senders

You can receive the notification in real time via a call to your server. To set it up go on Skebby.com > Log in > Settings > Send SMS > Alphanumeric sender approval/rejection notification and set up the sending protocol wanted (GET/POST/REST/SOAP) and the destination URL.



  • The parameters sent to the URL specified are:
    Parameter Description
    String alias Alphanumeric sender
    String vat_number VAT Number
    String business_name Business Name
    String status Status (APPROVED or REJECTED)


    Example of HTTP body:



  • For SOAP/REST requests, a method called "notifyAlias" has to be used with the following items:
    Parameter Description
    String alias Alphanumeric sender
    String vat_number VAT Number
    String business_name Business Name
    String status Status (APPROVED or REJECTED)

Sending Basic SMS

Sends a Basic SMS and replies with remaining SMS balance.

  • Url for HTTP requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/http.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/http.php

    Parameters has to be sent with POST method, in the standard urlencode. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms_basic
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in an Array form e.g.:

    recipients[]=393334455666&recipients[]=393334455667

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    The recipients string, in a multidimensional Array form, will be:
    recipients[0][recipient]=393471234567&recipients[0][nome]=Mario&recipients[1][recipient]=393477654321&recipients[1][nome]=Marco

    String text Message you want to send, maximum length 1549 characters "9.9935483870968 SMS concatenated in one message."

    New View invoicing billing to send long SMS (more than 160 chars)
    Chars Number of SMS charged
    0-160 1
    161-312 2
    313-468 3
    469-624 4
    625-780 5
    781-936 6
    937-1092 7
    1093-1248 8
    1249-1404 9
    1405-1560 10

    Optional parameters:
    Parameter Description
    String charset See note on use of charset
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822


    Example of HTTP body for sending multiple Basic SMS:



  • Url for REST requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/rest.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/rest.php

    Parameters of REST requests has to be sent with POST method. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms_basic
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in JSON Array form e.g.:

    recipients = [ "393334455666" , "393334455667" ];

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    The recipients string, in JSON Array form, will be:
    ?recipients=[{recipient:'393471234567',nome:'Mario'},{recipient:'393477654321',nome:'Marco'}]

    String text Message you want to send, maximum length 1549 characters "9.9935483870968 SMS concatenated in one message."

    New View invoicing billing to send long SMS (more than 160 chars)
    Chars Number of SMS charged
    0-160 1
    161-312 2
    313-468 3
    469-624 4
    625-780 5
    781-936 6
    937-1092 7
    1093-1248 8
    1249-1404 9
    1405-1560 10

    Optional parameters:
    Parameter Description
    String charset See note on use of charset
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822


    Example of REST body for sending multiple Basic SMS:



  • File wsdl with the description of the methods is available at this address:

    http://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl

    Compulsory parameters:
    Parameter Description
    String username Username you used to sign up
    String password Password you used to sign up
    Recipient[] recipients Array of recipients, in international format without + or 00

    New Customize text for every recipient
    Dynamic variables: it is possible to customize the text of the message for single recipient with dynamic variables (e.g.: “Name”) that allow to activate the variables with the specific value for each recipient. If you insert variables the total number of characters/SMS will be defined during sending in relation to the length of text variables for each contacts online.
    For example:
    Dear ${nome}, for you a 10% discount ticket on you next purchase. Show this SMS in the store.

    Recipients must be sent as an Array of Recipient objects, each containing the recipient number and possibly an Array of dynamic variables.

    String text Message you want to send, maximum length 1549 characters "9.9935483870968 SMS concatenated in one message."

    New View invoicing billing to send long SMS (more than 160 chars)
    Chars Number of SMS charged
    0-160 1
    161-312 2
    313-468 3
    469-624 4
    625-780 5
    781-936 6
    937-1092 7
    1093-1248 8
    1249-1404 9
    1405-1560 10

    Optional parameters:
    Parameter Description
    String delivery_start To schedule sending SMS, use format RFC 2822.
    View specification RFC 2822


  • How to use SMTP protocol to send SMS Basic from client/server email too
    To send SMS with SMTP protocol you need to enable the service by indicating which email account you want to use for sending. To set it up, go to Skebby.com > Sign in > Settings > Company name. If you want to send SMS from another account email, you will just have to add it. You can add as many accounts as you like.
    Parameter
    Parameter Description
    SMS Recipient The recipient of the SMS must be entered in the "A" or "CC" field using the following format: MOBILENUMBER@basic.skebby.com. The mobile number must be entered in international format, customers can choose from the example formats shown below:
    0039320XXXXXXX@basic.skebby.com
    +39320XXXXXXX@basic.skebby.com
    39320XXXXXXX@basic.skebby.com
    It is possible to send bulk messages up to 50 email/SMS simultaneously. If you send more than 50 email with this method the service will be suspended.

    Example: 00393334455666@basic.skebby.com
    Multiple recipients / Bulk sending To send up to 100 email/SMS you can send an SMS by entering each additional recipient to the "CC" field. To send greater than 100 and up to 50,000 email/SMS add the recipients in the standard format in the body of the email after the ## character that indicates the end of the text to be sent. You don’t need to enter spaces or any other chars between one recipient and the following.
    Sending to groups You can send an SMS to a group previously saved on Skebby.com > Login > Contacts > Groups by entering it in the "To" or "CC" field of the email using the following format:
    GROUPNAME@basic.skebby.com
    Example: colleagues@basic.skebby.com
    The group name must be one word, the same as the one saved on Skebby.com and contain at least one alphabetic char.
    To send SMS to the default group:
    • "Favorites" contacts send an email to favorites@basic.skebby.com
    • "Mobile address book" contacts send an email to mobileaddressbook@basic.skebby.com
    • All contacts send an email to allcontacts@basic.skebby.com
    Message text The message text must be written within the body of the email where you'd usually write the text of your email and the maximum lenght is 1549 characters ("9.9935483870968"). If you enter a text longer than 1549 characters the message will not be sent and you will be alert with an email. If the body of the email is empty, the email will be sent but the SMS will not arrive (no message charged).
    End of SMS The characters ## indicates the end of the text to be sent and it marks the end of the SMS. It must always be included. Any text after ## will not be sent.
    PIN Authentication You can request PIN authentication when sending SMS to email for greater security, by setting it up in your Skebby account settings. In order to send SMS by email the sender must include an address among the recipients, e.g.:. yourpin123@pin.skebby.com, where "yourpin123" corresponds to an alphanumeric security code (minimum 6 characters), which is indicated by the user in the Private Area i.e. Skebby.com > Sign in > Settings > Company name. If you choose PIN authentication, to send an SMS from any email address you've registered it will be compulsory to enter the email address with PIN as one of the recipients, otherwise the message will not be sent.


Sending Skebby 0cent SMS

Sends Skebby 0cent SMS to every user with Skebby on the mobile phone

  • Url for HTTP requests:

    http://gateway.skebby.it/api/send/smsskebby/advanced/http.php
    Secure https://gateway.skebby.it/api/send/smsskebby/advanced/http.php

    Parameters has to be sent with POST method, in the standard urlencode. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in an Array form e.g.:

    recipients[]=393334455666&recipients[]=393334455667
    String text Message you want to send, maximum length 1600
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666

    Optional parameters:
    Parameter Description
    String charset See note on use of charset


    Example of HTTP body for sending multiple Skebby 0cent SMS with numeric sender ID:

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/

  • Url for REST requests:

    http://gateway.skebby.it/api/send/smsskebby/advanced/rest.php
    Secure https://gateway.skebby.it/api/send/smsskebby/advanced/rest.php

    Parameters of REST requests has to be sent with POST method. It has been disable the GET method, because with many recipients the request may be cut.

    Compulsory parameters:
    Parameter Description
    String method send_sms
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in JSON Array form e.g.:

    recipients = [ "393334455666" , "393334455667" ];
    String text Message you want to send, maximum length 1600
    String sender_number* Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666

    Optional parameters:
    Parameter Description
    String charset See note on use of charset


    Example of REST body for sending multiple Skebby 0cent SMS with numeric sender ID:

    *For security reasons, the sender_number parameter is only enabled for those users who have verified their mobile number on our website used.
    To verify or modify your mobile number on our website you can use the following address:
    http://smsmessenger.skebby.com/
  • How to use SMTP protocol to send SMS Skebby 0cent from client/server email too
    To send SMS with SMTP protocol you need to enable the service by indicating which email account you want to use for sending. To set it up, go to Skebby.com > Sign in > Settings > Company name. If you want to send SMS from another account email, you will just have to add it. You can add as many accounts as you like.
    Parameter
    Parameter Description
    SMS Recipient The recipient of the SMS must be entered in the "A" or "CC" field using the following format: MOBILENUMBER@0cent.skebby.com. The mobile number must be entered in international format, customers can choose from the example formats shown below:
    0039320XXXXXXX@0cent.skebby.com
    +39320XXXXXXX@0cent.skebby.com
    39320XXXXXXX@0cent.skebby.com
    It is possible to send bulk messages up to 50 email/SMS simultaneously. If you send more than 50 email with this method the service will be suspended.

    Example: 00393334455666@0cent.skebby.com
    Multiple recipients / Bulk sending To send up to 100 email/SMS you can send an SMS by entering each additional recipient to the "CC" field. To send greater than 100 and up to 50,000 email/SMS add the recipients in the standard format in the body of the email after the ## character that indicates the end of the text to be sent. You don’t need to enter spaces or any other chars between one recipient and the following.
    Message text The message text must be written within the body of the email where you'd usually write the text of your email and the maximum lenght is 1600 characters. If you enter a text longer than 1600 characters the message will not be sent and you will be alert with an email. If the body of the email is empty, the email will be sent but the SMS will not arrive (no message charged).
    End of SMS The characters ## indicates the end of the text to be sent and it marks the end of the SMS. It must always be included. Any text after ## will not be sent.
    PIN Authentication You can request PIN authentication when sending SMS to email for greater security, by setting it up in your Skebby account settings. In order to send SMS by email the sender must include an address among the recipients, e.g.:. yourpin123@pin.skebby.com, where "yourpin123" corresponds to an alphanumeric security code (minimum 6 characters), which is indicated by the user in the Private Area i.e. Skebby.com > Sign in > Settings > Company name. If you choose PIN authentication, to send an SMS from any email address you've registered it will be compulsory to enter the email address with PIN as one of the recipients, otherwise the message will not be sent.

Testing sending SMS

Those methods do not actually send the SMS, you can use them to test the sending of Classic, Classic + and Basic SMS.



  • Compulsory parameters:
    Parameter Description
    String method
    • test_send_sms_classic
    • test_send_sms_classic_report
    • test_send_sms_basic
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in an Array form e.g.:

    recipients[]=393334455666&recipients[]=393334455667
    String text Message you want to send
    Maximum length:
    • Classic 1530 characters "10 SMS"
    • Basic 1549 characters "9.9935483870968 SMS"

    Optional parameters:
    Parameter Description
    String sender_number Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String charset See note on use of charset




  • Compulsory parameters:
    Parameter Description
    String method
    • test_send_sms_classic
    • test_send_sms_classic_report
    • test_send_sms_basic
    String username Username you used to sign up
    String password Password you used to sign up
    String[] recipients Recipient(s), in international format without + or 00, in JSON Array form e.g.:

    recipients = [ "393334455666" , "393334455667" ];
    String text Message you want to send
    Maximum length:
    • Classic 1530 characters "10 SMS"
    • Basic 1549 characters "9.9935483870968 SMS"

    Optional parameters:
    Parameter Description
    String sender_number Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]
    String charset See note on use of charset




  • Compulsory parameters:
    Parameter Description
    String username Username you used to sign up
    String password Password you used to sign up
    Recipient[] recipients Array of recipients, in international format without + or 00
    String text Message you want to send
    Maximum length:
    • Classic 1530 characters "10 SMS"
    • Basic 1549 characters "9.9935483870968 SMS"

    Optional parameters:
    Parameter Description
    String sender_number Allows you to specify any phone number you want as sender ID, the number must be in international format without + or 00, e.g.: 393334455666
    String sender_string Allows you to specify an alphanumeric string of maximum 11 characters to use as sender name, supported characters: [a-zA-Z0-9 .]




Check credit balance


  • Url for HTTP requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/http.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/http.php

    Compulsory parameters:
    Parameter Description
    String method get_credit - Compulsory for HTTP and REST
    String username Username you used to sign up
    String password Password you used to sign up

    Optional parameters:
    Parameter Description
    String charset See note on use of charset

    Example of HTTP body for checking credit balance:

    As an alternative you can check the credit balance on Skebby.com > Log in

  • Url for REST requests:

    http://gateway.skebby.it/api/send/smseasy/advanced/rest.php
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/rest.php

    Compulsory parameters:
    Parameter Description
    String method get_credit - Compulsory for HTTP and REST
    String username Username you used to sign up
    String password Password you used to sign up

    Optional parameters:
    Parameter Description
    String charset See note on use of charset

    As an alternative you can check the credit balance on Skebby.com > Log in

  • File wsdl with the description of the methods is available at this address:

    http://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl
    Secure https://gateway.skebby.it/api/send/smseasy/advanced/soapv3.php?wsdl

    Compulsory parameters:
    Parameter Description
    String username Username you used to sign up
    String password Password you used to sign up

    As an alternative you can check the credit balance on Skebby.com > Log in

Charset

For a SOAP request, the charset parameter must NOT be specified and will be ignored. For HTTP and REST protocols, the charset parameter can be set with one of the following values:
  • ISO-8859-1 (Default value)
  • UTF-8

Special characters

Some special characters, that has to be handle in a specific way, in the composition of the text message will be counted double in the global lenght of the SMS.

Special characters are the following:

Special character Description
[ Open square bracket
\ Backslash
] Close squade bracket
^ Caret
{ Open brace
| Vertical crossbar
} Close brace
~ Tilde
Euro symbol

Error codes

In case of a sending that contains a message addressed to a mobile phone repeated more than one time, the system allows the sending in asynchronous mode of the duplicated messages. In fact the message will be forwarded to the first mobile number, while the second/following ones will be rejected. By going on Skebby.com > Log in > Reports > SMS traffic and notifications > Traffic history you will visualize the error detail generated: "Duplicated recipients".

Error codes Meaning
10 Generic error
11 Invalid charset
12 A compulsory parameter has not been specified
20 Invalid parameters
21 Invalid username or password
22 Invalid sender ID
23 Sender ID too long (more than 11 characters)
24 Text too long
25 Invalid recipient
26 Sender ID not set
27 Too many recipients
29 Account not set to use gateway SMS
30 Not enough credit to send the message
31 Only request HTTP with POST method accepted
32 Invalis delivery_start format, use format RFC 2822 es: Mon, 15 Aug 2005 15:52:01 +0000
33 Invalid encoding_scheme, values accepted: normal, ucs2 view http://en.wikipedia.org/wiki/GSM_03.38 for more information.
34 Invalid validity_period, must be integer (express in minutes) bigger than 0 and smaller than 2880 (2 days)
35 Invalid user_reference, maximum lenght allowed 20 characters [a-zA-Z0-9-_+:;]
36 If you have set the delivery_start and you want the delivery report you have to specify the user_reference too
37 Some characters in the text are not valid for the charset specified, please check encoding parameter
38 There are too many alphanumeric senders with the same vat number
39 The vat number is not correct
40 Only business users can send an approval request for alphanumeric senders
41 Alphanumeric sender already approved


The maximum number of recipients that can be entered for a bulk send is 50.000, in order to send messages to up to 100.000 recipients, send an e-mail to support@skebby.com

Receive SMS



The "Receive SMS" service allows you to receive messages to a dedicated number or a shared number with keyword, directly on your own server through a HTTP / Rest / Soap call, via e-mail to the email addresses indicated on Skebby.com > Log in > Inboxes or forwarded to a Google Spreadsheet URL. When a text message is received, a server-to-server (s2s) call will be made from Skebby to the URL or email address set.

If you’re trying out the “Receive SMS” service at no cost with 100 free SMS, remember that you cannot send Basic or Classic SMS to test delivery, your text message must be sent from an Italian or foreign mobile via SIM.

Charset
the default charset parameter is ISO-8859-1. To edit it sign in to Skebby.com > Inboxes > Settings > Forward SMS on URL.

Types of forwarding available:

Email

Skebby will forward the message by e-mail, using the following parameters:
Parameter Description
String userDateTime Time the SMS arrives
String sender Number of SMS sender in international format without + or 00, e.g.: 393334455666
String text Message text

Google Drive Spreadsheet

Skebby will forward text message to the Google Drive Spreadsheet URL using the following parameters:
Parameter Description
String userDateTime Time the SMS arrives
String sender Number of SMS sender in international format without + or 00, e.g.: 393334455666
String text Message text
String contacts Contact name (if available in the Contact List)

http GET

Skebby will call the URL specified in the private area, passing the following parameters with GET:
Parameter Description
String sender Number of SMS sender in international format without + or 00, e.g.: 393334455666
String receiver Number the SMS was sent to in international format without + or 00, e.g.: 393334455666
String text Message text
String encoding Characters set used for the text (ISO-8859-1)
String date Date the SMS arrived
String time Time the SMS arrives
String timestamp SMS arrival timestamp for the developer’s convenience we pass three different date / time formats
String smsType Type of SMS received (standard or Skebby)

Example of HTTP body for receiving SMS with parameters in GET:

http POST

Skebby will call the URL specified in the private area, passing the following parameters with POST:
Parameter Description
String sender Number of SMS sender in international format without + or 00, e.g.: 393334455666
String receiver Number the SMS was sent to in international format without + or 00, e.g.: 393334455666
String text Message text
String encoding Characters set used for the text (ISO-8859-1)
String date Date the SMS arrived
String time Time the SMS arrives
String timestamp SMS arrival timestamp for the developer’s convenience we pass three different date / time formats
String smsType Type of SMS received (standard or Skebby)

Example of HTTP body for receiving SMS with parameters in POST:

REST

Skebby will call the URL specified in the private area, calling REST method "restGet" to which will pass the following parameters:
Parameter Description
String sender Number of SMS sender in international format without + or 00, e.g.: 393334455666
String receiver Number the SMS was sent to in international format without + or 00, e.g.: 393334455666
String text Message text
String encoding Characters set used for the text (ISO-8859-1)
String date Date the SMS arrived
String time Time the SMS arrives
String timestamp SMS arrival timestamp for the developer’s convenience we pass three different date / time formats
String smsType Type of SMS received (standard or Skebby)

Example of HTTP body for receiving SMS with parameters in REST:

SOAP

Skebby will call the URL specified in the private area, passing the SOAP method "smsin" with the following paramters (in the order thye have been indicated):
Parameter Description
String sender Number of SMS sender in international format without + or 00, e.g.: 393334455666
String receiver Number the SMS was sent to in international format without + or 00, e.g.: 393334455666
String text Message text
String date Date the SMS arrived
String time Time the SMS arrives
String timestamp SMS arrival timestamp for the developer’s convenience we pass three different date / time formats
String smsType Type of SMS received (standard or Skebby)

Example of HTTP body for receiving SMS with parameters in SOAP:




Nota bene

It is not allowed the use of API to send and receive SMS from mobile application of third parties if those have the purpose to publish on the market (App Store/Apple, Android Market/Google, App Store/Blackberry, Ovi Store/Nokia, Windows Phone Marketplace/Microsoft, Getjar, Mobango and every other market for mobile application in Italy or abroad). This is to avoid confusion between users or our app Skebby for mobile phone and those of third parties. For any other clarification or to find out more write us on support@skebby.com