{"id":290,"date":"2010-02-24T11:50:46","date_gmt":"2010-02-24T17:50:46","guid":{"rendered":"http:\/\/dmartenson.dc.multitech.prv\/developer\/?page_id=290"},"modified":"2010-04-01T13:07:51","modified_gmt":"2010-04-01T18:07:51","slug":"isms-send-api","status":"publish","type":"page","link":"https:\/\/www.multitech.net\/developer\/software\/isms\/isms-send-api\/","title":{"rendered":"iSMS Send API"},"content":{"rendered":"

HTTP Send API Format<\/strong><\/p>\n

Each “HTTP Send API Request” consists of four parts:
\n\u2022 The first part is the destination; i.e., the MultiModem iSMS IP and HTTP port number.
\n\u2022 The second part is the API call which is the query; therefore, it has a ‘?’ post-fixed to the call.
\n\u2022 The third part is for authentication, which is in the form of a username and password.
\n\u2022 The fourth part is the message parameters.<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=puser1&cat=1&to=\"7637175845\"&text=message<\/code><\/p>\n

Where, portnumber is optional and<\/p>\n

user1,puser1, 7637175845 and message are variable\/configured parameters.<\/p>\n

When HTTP Send API is enabled, it is also possible to send SMS from a non-browser with a TCP connection to the configured HTTP Port by following the steps below:
\n\u2022 Initiate a raw TCP connection to the MultiModem iSMS IP address over the “HTTP Send API” port
\nExample : telnet 192.168.2.1 81
\n\u2022 Issue GET command to send SMS.
\n\u2022 Issue GET command to query the status of send SMS.<\/p>\n

Send API Format<\/p>\n

GET \/sendmsg?user=admin&passwd=admin&cat=1[&enc=0][&priority=1][&modem=2]&to=5645676543&ton=Graham&group=Engineering&text=This%20is%20a%20test%20m
\nessage.^M^J<\/code><\/p>\n

Or<\/p>\n

GET \/sendmsg?user=admin&passwd=admin&cat=1[&enc=1][&priority=2][&modem=0]&to=%225678976543%22&ton=%22Bob%22&group=%22Engineering%22&text=This%20is%20a%20test%20message.^M^J<\/code><\/p>\n

Query API Format<\/p>\n

GET \/querymsg?user=admin&passwd=admin&apimsgid=message id.^M^J<\/code><\/p>\n

Note: All special characters must be given in URL encoded format with hex value; e.g., space should be given as %20; double quotes should be given as %22.
\nExample: If a name is Graham Bell, it should be given as Graham%20Bell<\/p>\n

Authentication<\/p>\n

The system needs to authenticate any API request. We achieve this by having the authentication credentials as part of the “Send SMS URL” or \u201cSend SMS TCP\u201d command.
\nuser – The username of the account, which has a maximum of 50 bytes.
\npasswd – The password of the account, which has a maximum of 50 bytes.
\nThis user should be Admin or the configured Send Users.
\nEvery “Send SMS URL” should have the username and password, and every request is authenticated by the MultiModem iSMS.<\/p>\n

Sending to a Number<\/p>\n

HTTP API format is:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=puser1&cat=1[
\n&enc=0][&priority=1][&modem=1]&to=\u201d7657867765\u201d&text=message
\n<\/code><\/p>\n

The parameters are:<\/p>\n

\u2022 cat Category
\n1 – Send SMS
\n2 – Broadcast Trigger
\n3 – Action Trigger<\/p>\n

\u2022 enc Encoding type to send SMS(Optional field)
\nRange: 0 to 3
\n0 – SMS text should be in ASCII form
\n1 – SMS text should be in Extended ASCII form
\n2 – SMS text should be in hexadecimal form (i.e. each hexadecimal value length
\nshould be maximum 4 and each hexadecimal value should be separated by a semi-colon. Example: 0645;41;646)
\n3 – SMS text should be in decimal form (i.e. each decimal Value length should be maximum 5 and each decimal value should be separated by a semi-colon.
\nExample: 1605;65;65300) Note: Maximum decimal value allowed is 65535
\nIf enc is not specified in the send API request, default enc will be the configured
\nsettings in SMS settings page .
\ni.e. enc=2, if Unicode is enabled.
\nenc=1, if Extended ASCII is enabled.
\nenc=0, if both Extended ASCII and Unicode are disabled.<\/p>\n

\u2022 priority Priority to send SMS (Optional field)
\nRange: 1 to 3
\n1 – Low Priority
\n2 – Normal Priority
\n3 – High Priority
\nIf priority is not specified in the request, default priority is normal.<\/p>\n

\u2022 modem Modem index to send SMS (this is only for the SF 400\/800 models)
\nRange : 1 to 4 for SF 400
\n1 to 8 for SF 800<\/p>\n

0 for any modem (Send API job will be distributed via all the available modems)
\nIf modem is not specified in the request, send API job will be distributed via all the
\navailable modems.
\n\u2022 to The mobile number where the SMS is to be delivered.
\nThis number has to be given within double quotes. The maximum size of each
\nrecipient\u2019s number is 50 bytes.
\n\u2022 text The message text to be sent.
\nEnable Extended ASCII in the MultiModem iSMS to send both ASCII and extended ASCII characters. By default, Extended ASCII is disabled and the message could have only ASCII characters.
\nNotes: If Extended ASCII and Unicode are disabled and spanned SMS value is 1, a maximum of 160 characters can be sent.
\nIf Extended ASCII is enabled and spanned SMS value is 1, a maximum of 140 characters can be sent.
\nIf Unicode is enabled and spanned SMS value is 1, a maximum of 70 characters can be sent.
\nIf the spanned SMS value is more than 1, the maximum number of characters allowed for each encoding scheme is defined as follows (where n represents the span value):
\nASCII \u2013 n * 154 characters
\nExtended ASCII \u2013 n * 134 characters
\nUnicode \u2013 n * 64 characters
\nAny characters entered beyond the allowed limit will be chopped off.
\nIn the HTTP API format example above: user1, puser1, 7657867765 and message are variables \/ configured parameters.<\/p>\n

Sending to an Address Book Name<\/p>\n

The API can be used to send the message to a name in the MultiModem iSMS address book. If the name does not exist in the address book, the message is dropped.<\/p>\n

HTTP API format is:
\nhttp:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=1
\n[&enc=0][priority=3][&modem=2]&ton=\u201dbob\u201d&text=message
\n<\/code><\/p>\n

or<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=1
\n[&enc=2][priority=3][&modem=2]&ton=\u201dbob\u201d&text=41;42;645;0645(hexadecimal form)
\n<\/code>
\nor<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=1
\n[&enc=3][priority=3][&modem=2]&ton=\u201dbob\u201d&text=65;66;67(decimal form)<\/code><\/p>\n

The parameters are:
\n\u2022 cat 1
\n\u2022 enc Encoding type to send SMS(Optional field)
\nRange: 0 to 3
\n0 – SMS text should be in ASCII form
\n1 – SMS text should be in Extended ASCII form
\n2 – SMS text should be in hexadecimal form (i.e. each hexadecimal value length
\nshould be maximum 4, and each hexadecimal value should be separated by
\na semi-colon. Example: 0645;41;646)
\n3 – SMS text should be entered in decimal form (i.e. each decimal Value length
\nshould be maximum 5, and each decimal value should be separated by a
\nsemi-colon. Example: 1605;65;65300)
\nNote: Maximum decimal value allowed is 65535.<\/p>\n

If enc is not specified in the send API request, default enc will be the configured
\nsettings in SMS settings page.
\ni.e. enc=2, if Unicode is enabled.
\nenc=1, if Extended ASCII is enabled.
\nenc=0, if both Extended ASCII and Unicode are disabled.<\/p>\n

\u2022 Priority Priority to send SMS(Optional field)
\nRange: 1 to 3
\n1 – Low Priority
\n2 – Normal Priority
\n3 – High Priority
\nIf priority is not specified in the request, the default priority is normal.<\/p>\n

\u2022 modem Modem index to send SMS (this is only for the SF 400\/800 models)
\nRange : 1 to 4 for SF 400
\n1 to 8 for SF 800
\n0 for any modem (Send API job will be distributed via all the available
\nmodems)
\nIf modem is not specified in the request, send API job will be distributed via all the
\navailable modems
\n\u2022 ton The name in the address book where the SMS is to be delivered must be given within
\ndouble quotes. The maximum size of each recipient’s name is 50 bytes.
\n\u2022 text The message text to be sent.
\nEnable Extended ASCII in the MultiModem iSMS to send both ASCII and extended
\nASCII characters. By default, Extended ASCII is disabled and the message can have only ASCII characters.
\nIf Unicode is enabled(if enc is not specified in request), SMS text should be only in Hexadecimal form.
\nIf Extended ASCII and Unicode are disabled and spanned SMS value is 1, a maximum of 160 characters can be sent.
\nIf Extended ASCII is enabled and spanned SMS value is 1, a maximum of 140 characters can be sent.
\nIf Unicode is enabled and spanned SMS value is 1, a maximum of 70 characters can be sent.
\nIf the spanned SMS value is more than 1, the maximum number of characters allowed for each encoding scheme is defined as follows (where n represents the span value):
\nASCII \u2013 n * 154 characters
\nExtended ASCII \u2013 n * 134 characters
\nUnicode \u2013 n * 64 characters
\nAny characters entered beyond the allowed limit will be chopped off.
\nSending to a Group
\nThe API can be used to send SMS to a pre-defined group. The group should exist in the MultiModem iSMS. If the group does not exist, the message is dropped.<\/p>\n

HTTP API format is:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=1
\n[enc=1][priority=1][&modem=4]&group=\u201dadmin\u201d&text=message<\/p>\n

<\/code>
\nor<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=1
\n[enc=2][priority=1][&modem=4]&group=\u201dadmin\u201d&text=41;42;645;0645(hexadecimal form)
\n<\/code>
\nor<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=1
\n[enc=3][priority=1][&modem=4]&group=\u201dadmin\u201d&text=65;66;678(decimalform)
\n<\/code>
\nThe parameters are:
\n\u2022 cat 1
\n\u2022 enc Encoding type to send SMS(Optional field)
\nRange: 0 to 3
\n0 – SMS text should be in ASCII form
\n1 – SMS text should be in Extended ASCII form
\n2 – SMS text should be in hexadecimal form (i.e. each hexadecimal value length
\nshould be maximum 4, and each hexadecimal value should be separated by
\na semi-colon. Example: 0645;41;646)
\n3 – SMS text should be in decimal form (i.e. each decimal Value length should
\nbe maximum 5, and each decimal value should be separated by a semi-colon
\nExample: 1605;65;65300)
\nNote: Maximum decimal value allowed is 65535.
\nIf enc is not specified in the send API request, default enc will be the configured settings from the SMS settings page.
\ni.e. enc=2, if Unicode is enabled.
\nenc=1, if Extended ASCII is enabled.
\nenc=0, if both Extended ASCII and Unicode are disabled.
\n\u2022 priority Priority to send SMS(Optional field)
\nRange: 1 to 3
\n1 – Low Priority
\n2 – Normal Priority
\n3 – High Priority<\/p>\n

If priority is not specified in the request, the default priority is normal.<\/p>\n

\u2022 modem Modem index to send SMS (this is only for the SF 400\/800 models)
\nRange : 1 to 4 for SF 400
\n1 to 8 for SF 800
\n0 for any modem (Send API job will be distributed via all the available
\nmodems)
\nIf modem is not specified in the request, send API job will be distributed via all the
\navailable modems.
\n\u2022 group The pre-defined group name(s) must be given within double quotes.
\nThe maximum size of group name is 50 bytes.
\n\u2022 text The message text to be sent.
\nEnable Extended ASCII in the MultiModem iSMS to send both ASCII and extended ASCII characters. By default, Extended ASCII is disabled, and the message can have only ASCII characters.
\nIf Unicode is enabled (and if enc is not specified in request), SMS text should only be in Hexadecimal form.
\nIf Extended ASCII and Unicode are disabled and spanned SMS value is 1, a maximum of 160 characters can be sent.
\nIf Extended ASCII is enabled and spanned SMS value is 1, a maximum of 140 characters can be sent.
\nIf Unicode is enabled and spanned SMS value is 1, a maximum of 70 characters can be sent.
\nIf the spanned SMS value is more than 1, the maximum number of characters allowed for each encoding scheme is defined as follows (where n represents the span value):
\nASCII \u2013 n * 154 characters
\nExtended ASCII \u2013 n * 134 characters
\nUnicode \u2013 n * 64 characters
\nAny characters entered beyond the allowed limit will be chopped off.<\/p>\n

Sending a Broadcast Trigger Message<\/p>\n

We can use the API to send a broadcast trigger message to the MultiModem iSMS.<\/p>\n

HTTP API format is:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user2&passwd=user2&cat=2
\n[&enc=0][&modem=5]&text=message
\n<\/code>
\nor<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user2&passwd=user2&cat=2
\n[&enc=2][&modem=5]&text=message should be hexadecimal form
\n<\/code>
\nor<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user2&passwd=user2&cat=2
\n[&enc=3][&modem=5]&text=message should be decimal form
\n<\/code>
\nThe parameters are:
\n\u2022 cat 2
\n\u2022 enc Encoding type to send SMS(Optional field)
\nRange: 0 to 3
\n0 – SMS text should be in ASCII form
\n1 – SMS text should be in Extended ASCII form
\n2 – SMS text should be in hexadecimal form (i.e. each hexadecimal value
\nlength should be maximum 4, and each hexadecimal value should be
\nseparated by a semi-colon. Example: 0645;41;646)
\n3 – SMS text should be in decimal form (i.e. each decimal Value length
\nshould be maximum 5, and each decimal value should be separated by a
\nsemi-colon. Example: 1605;65;65300)
\nNote: Maximum decimal value allowed is 65535.
\nIf enc is not specified in the send API request, default enc will be configured to the settings of the SMS settings page.
\ni.e. enc=2, if Unicode is enabled.
\nenc=1, if Extended ASCII is enabled.
\nenc=0, if both Extended ASCII and Unicode are disabled.
\n\u2022 modem Modem index to send broadcast message
\nRange : 1 to 4 for SF400
\n1 to 8 for SF800
\n0 for any modem (Broadcast API job will be distributed via all the available modems)
\nIf modem is not specified in the request, broadcast API job will be distributed via all the available modems
\nIf modem is specified, broadcast job will be sent via the specified modem.<\/p>\n

\u2022 text The trigger message text to be sent.
\nEnable Extended ASCII in the MultiModem iSMS to send both ASCII and extended ASCII characters.
\nBy default, Extended ASCII is disabled, and the message can have only ASCII characters.
\nIf Unicode is enabled (and if enc is not specified in request), SMS text should be only in Hexadecimal form.
\nIf Extended ASCII is disabled, a maximum of 160 characters can be sent.
\nIf Extended ASCII is enabled, a maximum of 140 characters can be sent.
\nIf Unicode is enabled, a maximum of 70 characters can be sent.
\nIrrespective of the spanned SMS value set, the maximum number of characters allowed in the text field is:
\n160 for ASCII
\n140 for Extended ASCII
\n70 for Unicode
\nAny characters entered beyond the allowed limit will be chopped off.
\nThe API can be used to send a trigger message to the MultiModem iSMS. If the MultiModem iSMS has a configured broadcast trigger, it will send the broadcast trigger message to the configured recipients.<\/p>\n

Sending an Action Trigger Message<\/p>\n

We could use this API to perform a predefined action.<\/p>\n

HTTP API format is:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=3
\n[&enc=0]&text=message
\n<\/code>
\nor<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&cat=3
\n[&enc=2]&text=message should be hexadecimal form
\n<\/code>
\nExample: Configured action trigger for adding preconfigured SMS as 41;42;43 (with enc=2).
\nPreconfigured SMS to add is 645;646;647;648 (in hexadecimal form).
\nIn an API request, the text field should be in the format:
\nConfigured action trigger;Preconfigured SMS
\ntext=41;42;43;;645;646;647;648 (not correct)
\ntext=41;42;43;3a;645;646;647;648 (correct format)
\nHere 3a is equivalent hexadecimal value for a semi-colon. We should use equivalent
\nhexadecimal value for either semi-colon or colon.<\/p>\n

or<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=3]&text=message should be decimal form.
\n<\/code>
\nExample: Configured action trigger for adding preconfigured SMS as 41;42;43(with enc=3).
\nPreconfigured SMS to add is 645;646;647;648 (in decimal form).
\nIn an API request, the text field should be in the format:
\nConfigured action trigger;Preconfigured SMS
\ntext=41;42;43;;645;646;647;648 (not correct)
\ntext=41;42;43;58;645;646;647;648 (correct format)
\nHere 58 is decimal equivalent value for a semi-colon. We should use equivalent decimal value for either semi-colon or colon.
\nIrrespective of the spanned SMS value set, the maximum number of characters allowed in the text field is:
\n160 for ASCII
\n140 for Extended ASCII
\n70 for Unicode<\/p>\n

Any characters entered beyond the allowed limit will be chopped off.<\/p>\n

Examples for action trigger with enc=2:
\nTo Add an entry in the Address book:
\nConfigured trigger: 41;42;43 (with enc=2)
\nName: 61;62;63;64 (abcd)
\nPhone number: 39;38;38;36;30;39;38;38;36;30 (9886098860)<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=41;42;43;3a;61;62;63;64;3a;39;38;38;36;30;39;38;38;36;30
\n<\/code>
\nHere 3a is the equivalent hexadecimal for semi-colon. Instead of 3a, we can use 3b (equivalent hexadecimal value for colon) also.<\/p>\n

To Add a group name:<\/p>\n

Configured trigger: 44;45;46 (with enc=2)
\nGroup name: 65;66;67;68 (efgh)<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=44;45;46;3b;65;66;67;68
\n<\/code>
\nTo Add a group name with a member and phone number:
\nConfigured trigger: 44;45;46 (with enc=2)
\nGroup name: 65;66;67;68 (efgh)
\nName: 61;62;63;64 (abcd)
\nPhone number: 39;38;38;36;30;39;38;38;36;30 (9886098860)<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=44;45;46;3b;65;66;67;68;3b;61;62;63;64;3b;39;38;38;36;30;39;38;38;36;30
\n<\/code>
\nTo Add a group name with a member (should exist in Address book):
\nConfigured trigger: 44;45;46(with enc=2)
\nGroup name: 65;66;67;68 (efgh)
\nName: 61;62;63;64 (abcd)<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=44;45;46;3b;65;66;67;68;3b;61;62;63;64<\/code><\/p>\n

To delete an entry in the Address Book:
\nConfigured trigger: 47;48;49(with enc=2)
\nName: 61;62;63;64 (abcd)
\nPhone number: 39;38;38;36;30;39;38;38;36;30 (9886098860)
\nWith Name and Number:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=47;48;49;3a;61;62;63;64;3a;39;38;38;36;30;39;38;38;36;30
\n<\/code>
\nWith Name only:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=47;48;49;3a;61;62;63;64<\/code><\/p>\n

With Number only:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=47;48;49;3a;3a;39;38;38;36;30;39;38;38;36;30<\/code><\/p>\n

To Delete a Group:<\/p>\n

Configured trigger: 4a;4b;4c (with enc=2)
\nGroup name: 65;66;67;68 (efgh)<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=user1&passwd=user1&
\ncat=3[&enc=2]&text=4a;4b;4c;3a;65;66;67;68
\n<\/code>
\nThe parameters are:
\n\u2022 cat 3
\n\u2022 enc Encoding type to send SMS(Optional field)
\nRange: 0 to 3
\n0 – SMS text should be in ASCII form
\n1 – SMS text should be in Extended ASCII form
\n2 – SMS text should be in hexadecimal form (i.e. each hexadecimal value length
\nshould be maximum 4, and each hexadecimal value should be separated by a
\nsemi-colon. Example: 0645;41;646)
\n3 – SMS text should be in decimal form (i.e. each decimal Value length should be
\nmaximum 5, and each decimal value should be separated by a semi-colon.
\nExample: 1605;65;65300). Note: Maximum decimal value allowed is 65535.
\nIf enc is not specified in the send API request, default enc will be the configured settings in SMS settings page .
\ni.e. enc=2, if Unicode is enabled.
\nenc=1, if Extended ASCII is enabled.
\nenc=0, if both Extended ASCII and Unicode are disabled.<\/p>\n

\u2022 Modem Modem index to send SMS
\nRange : 1 to 4 for SF400
\n1 to 8 for SF800
\n0 for any modem
\nSpecifying modem for a cat=3 job is not applicable. Action trigger is executed even if modem is specified.
\n\u2022 text The trigger message text to be sent.
\nEnable Extended ASCII in the MultiModem iSMS to send both ASCII and extended ASCII chars.
\nBy default, Extended ASCII is disabled, and the message can have only ASCII characters.
\nIf Unicode is enabled(if enc is not specified in request), SMS text should be only in Hexadecimal form.
\nIf Extended ASCII is disabled, a maximum of 160 characters can be sent.
\nIf Extended ASCII is enabled, a maximum of 140 characters can be sent.
\nIf Unicode is enabled, a maximum of 70 characters can be sent.
\nThe API can be used to send an action trigger to the MultiModem iSMS. If the MultiModem iSMS has a configured action trigger, it will perform the configured action.
\nSending to Multiple Numbers, Address Book Recipients or Groups
\nAn SMS can be sent to multiple numbers, address book names and groups using a single API.<\/p>\n

HTTP API format is:<\/p>\n

http:\/\/192.168.2.1[:portnumber]\/sendmsg?user=xxx&passwd=xxx&cat=1[&enc=0][&priority=1][&modem=8]&to=\u201dxxx1\u201d,\u201dxxx2\u201d,\u201dxxx3\u201d&ton=\u201dname1\u201d,\u201dname
\n2\u201d&group=\u201dadmin\u201d,\u201drd\u201d,\u201dmarket\u201d&text=message
\n<\/code><\/p>\n

xxx1, xxx2 and xxx3 are mobile numbers.
\nname1 and name2 are names in the Address Book.
\nadmin, rd and market are groups present in the MultiModem iSMS.
\nNote: The to, ton and group parameters should be enclosed in quotes.
\nResponse from the MultiModem iSMS after Submitting the Send SMS API
\nThe MultiModem iSMS returns a unique identifier; i.e. an API message ID for each “Send API request”.
\nThis ID can be used to track and monitor any given message.
\nID: apimsgid
\n-or-
\nErr: error code
\ne.g.,
\nID: 1
\nErr: 601<\/p>\n","protected":false},"excerpt":{"rendered":"

HTTP Send API Format Each “HTTP Send API Request” consists of four parts: \u2022 The first part is the destination; i.e., the MultiModem iSMS IP and HTTP port number. \u2022 The second part is the API call which is the query; therefore, it has a ‘?’ post-fixed to the call. \u2022 The third part is […]<\/p>\n","protected":false},"author":5,"featured_media":0,"parent":88,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"footnotes":""},"class_list":["post-290","page","type-page","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/290","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/comments?post=290"}],"version-history":[{"count":10,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/290\/revisions"}],"predecessor-version":[{"id":587,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/290\/revisions\/587"}],"up":[{"embeddable":true,"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/pages\/88"}],"wp:attachment":[{"href":"https:\/\/www.multitech.net\/developer\/wp-json\/wp\/v2\/media?parent=290"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}