HTTPS API v2 / Own messages' identifiers (unique_id)

 

With dispatch messages, in addition to the identifiers returned by the system SerwerSMS.pl, The customer can define their own identifiers for messages reported. Is this purpose, a variable "unique_id" and can accept alphanumeric values ​​of a-z, A-Z and 0-9, and the minimum length of 3 characters and a maximum of 50 characters.

Messages from your own identifiers can be sent either as individual messages as well as a group or personalized. For a single message, simply add the query variable unique_id and the value given by the customer, eg .:

POST:
{
   "username":"demo",
   "password":"demo",
   "phone":"+48500600700",
   "text":"message",
   "unique_id":"123abc1"
}

For mass dispatch, you must specify a list of identifiers unique_id in the order in which they are transmitted consecutive numbers. Another identifiers unique_id should be elements in the array, eg .:

POST:
{
   "username":"demo",
   "password":"demo",
   "phone":[{
      "+48500600700",
      "+48500600600",
      "+48500600500"
   }]
   "text":"message",
   "unique_id":[{
      "123abc1",
      "123abc2",
      "123abc3"
   }]
}

 

In the above example, the numbers have the following identifiers unique_id:
+48500600700 – 123abc1
+48500600600 – 123abc2
+48500600500 – 123abc3

The situation is similar in the case of sending personalized messages. The next unique_id identifiers should correspond to the reported messages along with the numbers.

The number of grouped numbers / personalized messages and unique_id identifiers must match. If the quantities do not match, none of the messages will be sent and the system will return a general error. The same applies to the values of unique_id identifiers. If at least one identifier contains unacceptable characters, a general error will be returned.