Inbound SMS
List SMS relay actions
getReturns a list of all actions available for use on your account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: name | Type: String |
Description:
The name of the action |
| Field: description | Type: String |
Description:
Action description curl [[DOMAIN]]v2/sms-relay/geo/actions |
Send a Sample Request
Code Examples
Success Response Example
List SMS relays
getReturns a list of all available SMS relay numbers on the account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: prefix | Type: String | Required: No |
Description:
An optional filter to only show numbers matching the specified query. Can accept * as a wildcard. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: String |
Description:
The ID of the relay object |
| Field: prefix | Type: String |
Description:
The prefix being affected |
| Field: action | Type: Object |
Description:
The relay action associated with the prefix |
| Field: action.name | Type: String |
Description:
The relay action name. Possible values are: black_hole, http_get, http_post, email, mvno If the action type of a prefix is currently set to 'mvno', this means that the messages cannot be forwarded to any external destination |
| Field: action.description | Type: String |
Description:
The relay action description |
| Field: action.parameters | Type: Array |
Description:
The parameters associated with the action. The values will depend on the selected action type For example, a list of destination email addresses in case of 'email' action or a list of http endpoints for 'http_get' or 'http_post' actions |
| Field: updated_at | Type: Datetime |
Description:
The time of the most recent update |
Send a Sample Request
Code Examples
Success Response Example
Show SMS relay
getReturns a single SMS relay object
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: relay | Type: String | Required: Yes |
Description:
The alphanumeric ID of SMS relay object to show |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: String |
Description:
The ID of the relay object |
| Field: prefix | Type: String |
Description:
The prefix being affected |
| Field: action | Type: Object |
Description:
The relay action associated with the prefix |
| Field: action.name | Type: String |
Description:
The relay action name. Possible values are: black_hole, http_get, http_post, email, mvno If the action type of a prefix is currently set to 'mvno', this means that the messages cannot be forwarded to any external destination |
| Field: action.description | Type: String |
Description:
The relay action description |
| Field: action.parameters | Type: Array |
Description:
The parameters associated with the action. The values will depend on the selected action type For example, a list of destination email addresses in case of 'email' action or a list of http endpoints for 'http_get' or 'http_post' actions |
| Field: updated_at | Type: Datetime |
Description:
The time of the most recent update |
Send a Sample Request
Code Examples
Success Response Example
Update SMS relay
patchUpdate an SMS relay object
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: relay | Type: String | Required: Yes |
Description:
The alphanumeric ID of SMS relay object to update |
| Parameter: action | Type: String | Required: Yes |
Description:
The name of the action to be assigned. Accepted values are: black_hole, http_get, http_post, email If you modify the action type from 'mvno' to some other method of delivery, this will mean that MT messages will no longer be delivered to the MVNO sim this prefix is associated with. It is important to note that you will not be able to set the action type to 'mvno' without having special permissions enabled on your account. |
| Parameter: parameters | Type: Array | Required: Yes |
Description:
The array of parameters for the selected action. The values will depend on the selected action type. This can be either a list of destination email addresses for the 'email' action or a list of HTTP endpoints for 'http_get' or 'http_post' actions. This is a required parameter unless the selected action type is 'black_hole' or 'mvno'. When using either 'http_get' or 'http_post' as the relay action, you can pass in variable placeholders into the return URL. They will be replaced by corresponding values at runtime. The following placeholders are available: %m: Message %o: Originator %d: Destination %t: Timestamp in 'yyyy-mm-dd hh:mm:ss' %x: Timestamp in Unix time %u: UDH %i: Message ID |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: String |
Description:
The ID of the relay object |
| Field: prefix | Type: String |
Description:
The prefix being affected |
| Field: action | Type: Object |
Description:
The relay action associated with the prefix |
| Field: action.name | Type: String |
Description:
The relay action name. Possible values are: black_hole, http_get, http_post, email, mvno If the action type of a prefix is currently set to 'mvno', this means that the messages cannot be forwarded to any external destination |
| Field: action.description | Type: String |
Description:
The relay action description |
| Field: action.parameters | Type: Array |
Description:
The parameters associated with the action. The values will depend on the selected action type This can be either a list of destination email addresses for the 'email' action or a list of HTTP endpoints for 'http_get' or 'http_post' actions |
| Field: updated_at | Type: Datetime |
Description:
The time of the most recent update |
Send a Sample Request
Code Examples
Success Response Example
Network lookup
Lookup query
getPerform HLR lookup on a number to get information about it's home network - Cost 1 SMS credit per lookup
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: number | Type: String | Required: Yes |
Description:
The MSISDN (mobile number) to perform the lookup on. The number should not contain any special characters and begin with a country code without leading zeros or '+' sign. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: number | Type: String |
Description:
The lookup subject number |
| Field: status | Type: Object |
Description:
Lookup status. It can contain different status codes depending on response from mobile provider |
| Field: mcc | Type: String |
Description:
Mobile Country Code |
| Field: mnc | Type: String |
Description:
Mobile Network Code |
| Field: network | Type: Object |
Description:
Network info. It contains the name, country and contact details (if available) of the number's home network |
| Field: imsi | Type: String |
Description:
International Mobile Subscriber Identity. The IMSI is a unique number identifying a GSM subscriber |
| Field: ported | Type: Boolean |
Description:
Is it a ported number |
| Field: roaming | Type: Boolean |
Description:
Is the number roaming |
Send a Sample Request
Code Examples
Success Response Example
Outbound SMS
Check available credit
getCheck the available credit amount on your account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Send a Sample Request
Code Examples
Success Response Example
Delete pending SMS
deleteAllows for deleting pending SMS messages. It is only possible to delete one message at a time.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: message | Type: Integer | Required: Yes |
Description:
The message ID |
Error Fields (Error 4xx)
| Field | Type | Description |
|---|---|---|
| Field: message | Type: String |
Description:
Error message |
Send a Sample Request
Code Examples
Success Response Example
Get pending SMS
getGet a list of pending SMS messages which have not yet been sent. Multipart messages will be displayed separately.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: Integer |
Description:
The ID of the pending message |
| Field: source | Type: String |
Description:
The name or number of the sender |
| Field: destination | Type: String |
Description:
The destination number (MSISDN) |
| Field: received | Type: Datetime |
Description:
The time when the message was registered by our system |
| Field: scheduled_delivery | Type: Datetime |
Description:
The scheduled delivery time |
| Field: original_scheduled_delivery | Type: Datetime |
Description:
The original scheduled delivery time It will be the same as scheduled_delivery unless the initial message delivery fails and is rescheduled in the system |
| Field: data | Type: String |
Description:
The message body |
Error Fields (Error 4xx)
| Field | Type | Description |
|---|---|---|
| Field: message | Type: String |
Description:
Error message |
Send a Sample Request
Code Examples
Success Response Example
Preview SMS
post"Fake" sending an SMS message to view how it will be handled by the service, how it will be split and how much credit will be used.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: destinations | Type: Array | Required: Yes |
Description:
An array containing destination numbers to which the message will be sent. The destination numbers must be digits only without any special characters or spaces, and must begin with a country code (E.164 compliant) without leading zeros |
| Parameter: message | Type: String | Required: Yes |
Description:
Message body |
| Parameter: originator | Type: String | Required: No |
Description:
The message sender name to be shown. |
| Parameter: send_time | Type: String | Required: No |
Description:
Specific date and time on which the message should be sent. If not specified it will be sent instantaneously. |
| Parameter: dlr_url | Type: String | Required: No |
Description:
A [GET] URL on your server where the delivery report should be sent. |
| Parameter: max_parts | Type: Integer | Required: No |
Description:
Maximum number of concatenated parts the message can be split into. If the message is too long to fit within the chosen limit, only part of it will be delivered. |
| Parameter: replace | Type: Boolean | Required: No |
Description:
Replaceable Messages are messages which are allowed to be updated by newer versions of themselves. Both the original and replacement messages must be sent as Replaceable Messages with the same originator. |
| Parameter: flash | Type: Boolean | Required: No |
Description:
Flash SMS is an SMS which is displayed on the phone screen immediately upon arrival. If several flash messages are sent to one phone, only the latter message will be displayed. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: message_parts | Type: Integer |
Description:
The number of parts the message will be split into |
| Field: credit_cost | Type: Integer |
Description:
Number of credits required for sending the message |
| Field: available_credit | Type: Integer |
Description:
Amount of credits currently available on the account |
| Field: message_meta | Type: Object |
Description:
Additional information about the message |
Error Fields (Error 4xx)
| Field | Type | Description |
|---|---|---|
| Field: message | Type: String |
Description:
Error message |
| Field: errors | Type: String |
Description:
List of request parameters that failed validation |
Send a Sample Request
Code Examples
Success Response Example
Send SMS
postSend a message to one or more specified destination numbers. In the case of multipart messages, the credit cost is calculated by multiplying the number of parts by the number of recipients.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: destinations | Type: Array | Required: Yes |
Description:
An array containing destination numbers to which the message will be sent. The destination numbers must be digits only without any special characters or spaces, and must begin with a country code (E.164 compliant) without leading zeros. Please note, we only perform basic validation on the destination numbers and we suggest performing additional validation before submitting the request. Using Network Lookup is recommended to ensure the destination number exists and is reachable. |
| Parameter: message | Type: String | Required: Yes |
Description:
Message body |
| Parameter: originator | Type: String | Required: No |
Description:
The message sender name to be shown. |
| Parameter: send_time | Type: String | Required: No |
Description:
Specific date and time on which the message should be sent. If not specified it will be sent instantaneously. |
| Parameter: dlr_url | Type: String | Required: No |
Description:
A [GET] URL on your server where the delivery report should be sent. eg: https://www.site.com/dlr.php?reportcode=%code&destinationnumber=%dest&msgid=%msgid&dlr=%dlr&ts=%timestamp |
| Parameter: max_parts | Type: Integer | Required: No |
Description:
Maximum number of concatenated parts the message can be split into. If the message is too long to fit within the chosen limit, only part of it will be delivered. |
| Parameter: replace | Type: Boolean | Required: No |
Description:
Replaceable Messages are messages which are allowed to be updated by newer versions of themselves. Both the original and replacement messages must be sent as Replaceable Messages with the same originator. |
| Parameter: flash | Type: Boolean | Required: No |
Description:
Flash SMS is an SMS which is displayed on the phone screen immediately upon arrival. If several flash messages are sent to one phone, only the latter message will be displayed. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: Integer |
Description:
The ID of the pending message |
| Field: source | Type: String |
Description:
The sender name or number |
| Field: destination | Type: String |
Description:
The destination number (MSISDN) |
| Field: received | Type: Datetime |
Description:
The time of the message being registered by our system |
| Field: scheduled_delivery | Type: Datetime |
Description:
The scheduled delivery time |
| Field: original_scheduled_delivery | Type: Datetime |
Description:
The original scheduled delivery time It will be the same as scheduled_delivery unless the initial message delivery fails and is rescheduled in the system |
| Field: data | Type: String |
Description:
The message body |
Error Fields (Error 4xx)
| Field | Type | Description |
|---|---|---|
| Field: message | Type: String |
Description:
Error message |
| Field: errors | Type: String |
Description:
List of request parameters that failed validation |
Send a Sample Request
Code Examples
Success Response Example
Error Response Example
Error-Response:
HTTP/1.1 402 Payment Required
{
"message": "Insufficient credit."
}
Error-Response:
HTTP/1.1 422 Unprocessable Entity
{
"message": "Request validation failed.",
"errors": "The destinations.0 format is invalid."
}
Send vCard
postSend contact details as a vCard via SMS.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: destinations | Type: Array | Required: Yes |
Description:
An array containing destination numbers to which the vCard will be sent. The destination numbers must be digits only without any special characters or spaces, and must begin with a country code (E.164 compliant) without leading zeros |
| Parameter: first_name | Type: String | Required: Yes |
Description:
The contact's first name |
| Parameter: last_name | Type: String | Required: Yes |
Description:
The contact's last name |
| Parameter: phone | Type: Array | Required: No |
Description:
An array containing contact's phone numbers |
| Parameter: phone.mobile | Type: String | Required: No |
Description:
Mobile phone number |
| Parameter: phone.home | Type: String | Required: No |
Description:
Home phone number |
| Parameter: phone.work | Type: String | Required: No |
Description:
Work phone number |
| Parameter: phone.fax | Type: String | Required: No |
Description:
Fax number |
| Parameter: email | Type: String | Required: No |
Description:
The contact's email |
| Parameter: birth_date | Type: String | Required: No |
Description:
The contact's birth date |
| Parameter: note | Type: String | Required: No |
Description:
Additional note |
| Parameter: originator | Type: String | Required: No |
Description:
The vCard sender name to be shown. |
| Parameter: send_time | Type: String | Required: No |
Description:
Specific date and time on which the vCard should be sent. If not specified it will be sent instantaneously. |
| Parameter: dlr_url | Type: String | Required: No |
Description:
A [GET] URL on your server where the delivery report should be sent. eg: https://www.site.com/dlr.php?reportcode=%code&destinationnumber=%dest&msgid=%msgid |
| Parameter: version | Type: String | Required: No |
Description:
The Vcard protocol version to use (2.1 | 3.0 | 4.0). If not specified, 3.0 is used. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: Integer |
Description:
The ID of the pending message |
| Field: source | Type: String |
Description:
The sender name or number |
| Field: destination | Type: String |
Description:
The destination number (MSISDN) |
| Field: received | Type: Datetime |
Description:
The time of the message being registered by our system |
| Field: scheduled_delivery | Type: Datetime |
Description:
The scheduled delivery time |
| Field: original_scheduled_delivery | Type: Datetime |
Description:
The original scheduled delivery time It will be the same as scheduled_delivery unless the initial message delivery fails and is rescheduled in the system |
| Field: data | Type: String |
Description:
The message body |
Send a Sample Request
Code Examples
Success Response Example
SIP
Download CDR archive
getDownload zip file containing prepared CDR data in CSV format.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: handle | Type: String | Required: Yes |
Description:
The request identifier received from 'v2/cdr/request' call. |
Send a Sample Request
Code Examples
Request CDR download
postRequest Call Detail Records for specific time period as downloadable archive containing CSV files. This will create a request for the data to be prepared for download. Requests will expire after 2 hours from being submitted. If the data is not downloaded by that time, a new request will need to be submitted. Please note, all dates (submitted and returned) are in UTC.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: from_date | Type: String | Required: Yes |
Description:
Start date for CDR lookup (required) |
| Parameter: to_date | Type: String | Required: Yes |
Description:
End date for CDR lookup (required) |
| Parameter: email | Type: String | Required: No |
Description:
Email address to which a confirmation will be sent when the requested data is ready. |
| Parameter: format | Type: String | Required: No |
Description:
Please note: the UKv3a format is now the current default CDR layout as of 30/09/2021 23:59. The UKv3 format is no longer supported. |
| Parameter: single_file | Type: Boolean | Required: No |
Description:
When set to true, all of the data will be put into single CSV file instead of being split by days. |
Send a Sample Request
Code Examples
Success Response Example
Cancel CDR request
deleteCancel a download request.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: handle | Type: String | Required: Yes |
Description:
The request identifier received from 'v2/cdr/request' call. |
Send a Sample Request
Code Examples
Success Response Example
Check CDR request
getCheck the status of previously submitted request. If it has been processed, the response meta element will contain a download link. This will create a request for the data to be prepared for download.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: handle | Type: String | Required: Yes |
Description:
The request identifier received from 'v2/cdr/request' call. |
Send a Sample Request
Code Examples
Success Response Example
Refresh CDR request to extend the expiry time.
putRefresh a request. The request expiry timer will be reset.
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: handle | Type: String | Required: Yes |
Description:
The request identifier received from 'v2/cdr/request' call. |
Send a Sample Request
Code Examples
Success Response Example
Get SIP trunk info
getGet SIP trunk related information for current account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: balance | Type: Integer |
Description:
Current account balance |
| Field: channels | Type: Integer |
Description:
Maximum number of channels |
| Field: tariff_name | Type: String |
Description:
The name of tariff currently being used |
Send a Sample Request
Code Examples
Success Response Example
Get SIP trunk source IPs
getGet SIP trunk source IPs for current account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: limit | Type: Integer | Required: No |
Description:
Maximum records to return (optional - default all) |
| Parameter: offset | Type: Integer | Required: No |
Description:
Skip this number of records from start (optional - default 0) |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: source_ips | Type: Array |
Description:
All source IPs for current account |
Send a Sample Request
Code Examples
Success Response Example
VMN Inbound SMS
List SMS relay actions
getReturns a list of all actions available for use on your account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: name | Type: String |
Description:
The name of the action |
| Field: description | Type: String |
Description:
Action description curl [[DOMAIN]]v2/sms-relay/vmn/actions |
Send a Sample Request
Code Examples
Success Response Example
List VMN SMS relays
getReturns a list of all available Virtual Mobile Numbers SMS relays on the account
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: number | Type: String | Required: No |
Description:
An optional filter to only show numbers matching the specified query. Can accept * as a wildcard. |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: String |
Description:
The ID of the relay object |
| Field: number | Type: String |
Description:
The number being affected |
| Field: action | Type: Object |
Description:
The relay action associated with the number |
| Field: action.name | Type: String |
Description:
The relay action name. Possible values are: inactive, http_get, http_post, email, dialogue_post, dialogue_get, ms_outlook, desktopsms, inbound_gw |
| Field: action.description | Type: String |
Description:
The relay action description |
| Field: action.parameters | Type: Array |
Description:
The parameters associated with the action. The values will depend on the selected action type For example, a list of destination email addresses in case of 'email' action or a list of http endpoints for 'http_get' or 'http_post' actions |
| Field: updated_at | Type: Datetime |
Description:
The time of the most recent update |
Send a Sample Request
Code Examples
Success Response Example
Show VMN SMS relay
getReturns a single Virtual Mobile Number SMS relay object
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: relay | Type: String | Required: Yes |
Description:
The alphanumeric ID of SMS relay object to show |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: String |
Description:
The ID of the relay object |
| Field: number | Type: String |
Description:
The number being affected |
| Field: action | Type: Object |
Description:
The relay action associated with the number |
| Field: action.name | Type: String |
Description:
The relay action name. Possible values are: inactive, http_get, http_post, email, dialogue_post, dialogue_get, ms_outlook, desktopsms, inbound_gw |
| Field: action.description | Type: String |
Description:
The relay action description |
| Field: action.parameters | Type: Array |
Description:
The parameters associated with the action. The values will depend on the selected action type For example, a list of destination email addresses in case of 'email' action or a list of http endpoints for 'http_get' or 'http_post' actions |
| Field: updated_at | Type: Datetime |
Description:
The time of the most recent update |
Send a Sample Request
Code Examples
Success Response Example
Update VMN SMS relay
patchUpdate a Virtual Mobile Number SMS relay object
Header
| Header | Type | Required | Description |
|---|---|---|---|
| Header: X-Auth-Token | Type: String | Required: Yes |
Description:
Your API token. |
| Header: Content-Type | Type: String | Required: Yes |
Description:
Request content type. |
Parameter
| Parameter | Type | Required | Description |
|---|---|---|---|
| Parameter: relay | Type: String | Required: Yes |
Description:
The alphanumeric ID of SMS relay object to update |
| Parameter: action | Type: String | Required: Yes |
Description:
The name of the action to be assigned. Accepted values are: inactive, http_get, http_post, email, dialogue_post, dialogue_get, ms_outlook, desktopsms, inbound_gw |
| Parameter: parameters | Type: Array | Required: Yes |
Description:
The array of parameters for the selected action. The values will depend on the selected action type. This can be either a list of destination email addresses for the 'email' action or a list of HTTP endpoints for 'http_get' or 'http_post' actions. This is a required parameter unless the selected action type is 'inactive'. When using either 'http_get' or 'http_post' as the relay action, you can pass in variable placeholders into the return URL. They will be replaced by corresponding values at runtime. The following placeholders are available: %id: A unique identifier for the message %stat: Message Status: 0 (Normal Message), 1 (Concatenated message), 2 - (Indecipherable UDH - possibly corrupt message) %orig: The sender's number %dest: The destination number %msg: The message body %time: Time the message was received (UK time). Format: YYYY-MM-DD HH:MM:SS %timeZone: An integer, indicating time zone (eg: if timeZone is 1 then it means smsTime is GMT + 1) %smsTime: Time when the sms was sent. Format: YYYY-MM-DD HH:MM:SS %netw: Name of the originating network. Will be replaced with an SMSC reference number if the network is not recognised. %code: Message coding - 7 (GSM), 8 (binary) or 16 (Unicode) %udh: The User Data Header of the message |
Response Fields (Success 200)
| Field | Type | Description |
|---|---|---|
| Field: id | Type: String |
Description:
The ID of the relay object |
| Field: number | Type: String |
Description:
The number being affected |
| Field: action | Type: Object |
Description:
The relay action associated with the number |
| Field: action.name | Type: String |
Description:
The relay action name. Possible values are: inactive, http_get, http_post, email, dialogue_post, dialogue_get, ms_outlook, desktopsms, inbound_gw |
| Field: action.description | Type: String |
Description:
The relay action description |
| Field: action.parameters | Type: Array |
Description:
The parameters associated with the action. The values will depend on the selected action type This can be either a list of destination email addresses for the 'email' action or a list of HTTP endpoints for 'http_get' or 'http_post' actions |
| Field: updated_at | Type: Datetime |
Description:
The time of the most recent update |