Contents
HTTP API 4.0 is platform independent.
Thus it possible to integrate the product with any solution, regardless of the technologies and programming languages used.
HTTP API 4.0 provides the following capabilities:
- Sending SMS messages in ASCII format (Latin)
- Sending SMS messages in UNICODE format
- Sending long (concatenated) SMS messages
- Sending VIBER messages
- SMS or VIBER message status tracking
- Message scheduling
- Message sending speed control
- Account balance inquiry
- Preliminary calculation of messages sending cost
- Request SMS and VIBER registered Sender Names
Data transfer is carried out by means of data exchange within the application layer protocol. Data is exchanged via the HTTPS protocol, i.e. HTTP (RFC 2068, RFC 2616) with the mandatory use of the SSL/TLS layer.
Server handles incoming connections on port 444 .
Server accepting requests in JSON format by using POST method.
HTTP API 4.0 has following limitations:
1. Within a single request, SMS messages can be sent to no more than 20 000 recipients.
2. Within a single request, VIBER messages can be sent to no more than 100 000 recipients.
3. Within a single request, can be requested up to 20 000 statuses.
4. HTTP API 4.0 accepts only one request at a time for the same account.
5. Recipient's mobile number must be indicated in international format (max. 15 digits).
6. The maximum length of the SMS message is 500 symbols (including spaces and punctuation).
7. The maximum length of the VIBER message is 1000 symbols (including spaces and punctuation).
8. In case of sending VIBER message. If the button text is specified but the URL is not specified, the message will not be sent. And vise versa.
9. To successfully submit messages to the server, you must also:
1. Within a single request, SMS messages can be sent to no more than 20 000 recipients.
2. Within a single request, VIBER messages can be sent to no more than 100 000 recipients.
3. Within a single request, can be requested up to 20 000 statuses.
4. HTTP API 4.0 accepts only one request at a time for the same account.
5. Recipient's mobile number must be indicated in international format (max. 15 digits).
6. The maximum length of the SMS message is 500 symbols (including spaces and punctuation).
7. The maximum length of the VIBER message is 1000 symbols (including spaces and punctuation).
8. In case of sending VIBER message. If the button text is specified but the URL is not specified, the message will not be sent. And vise versa.
9. To successfully submit messages to the server, you must also:
- Set the account currency in the MOBIPACE system, in the “Profile” section.
- Send messages only from registered sender names. Sender names must first be agreed with your account manager.
Data transfer is carried out by means of data exchange within the application layer protocol. Data is exchanged via the HTTPS protocol, i.e. HTTP (RFC 2068, RFC 2616) with the mandatory use of the SSL/TLS layer.
Server handles incoming connections on port 444.
Server accepting requests in JSON format by using POST method.
There are eleven request methods in HTTP API 4.0.
Each of the eleven methods uses its own URL.
The data exchange between the Partner’s software and the HTTP API 4.0 must be interpreted in JSON format.
All responses from MOBIPACE system are also interpreted in JSON format. The Partner must ensure the correct recognition of the JSON data received from the MOBIPACE.
The maximum responce time for any request should not exceed 60 seconds. If there is no response, it's necessary to check the connection status with the system.
Server handles incoming connections on port 444.
Server accepting requests in JSON format by using POST method.
There are eleven request methods in HTTP API 4.0.
- Authorize
- SendSMS
- CalculateSMS
- QuerySMSBalance
- QuerySMSMessages
- RegisteredSMSSenderNames
- SendViber
- CalculateViber
- QueryViberBalance
- QueryViberMessages
- RegisteredViberSenderNames
Each of the eleven methods uses its own URL.
The data exchange between the Partner’s software and the HTTP API 4.0 must be interpreted in JSON format.
All responses from MOBIPACE system are also interpreted in JSON format. The Partner must ensure the correct recognition of the JSON data received from the MOBIPACE.
The maximum responce time for any request should not exceed 60 seconds. If there is no response, it's necessary to check the connection status with the system.
You must first authorize on the MOBIPACE server to be able to send messages.
Upon successful authorization, the system opens session with the assignment of a unique ID. This ID should be used by Partner to send requests to HTTP APi 4.0.
Session timeout set to 20 minutes from last request. Upon timeout, the server automatically closes the session. If session expired, it is necessary to go through the authorization process again to generate new session ID.
URL for authorization:
Server accepting requests in JSON format by using POST method.
Parameters expected in the authorization request:
MOBIPACE system responce:
JSON request example for authorization:
Server responce example:
Upon successful authorization, the system opens session with the assignment of a unique ID. This ID should be used by Partner to send requests to HTTP APi 4.0.
Session timeout set to 20 minutes from last request. Upon timeout, the server automatically closes the session. If session expired, it is necessary to go through the authorization process again to generate new session ID.
URL for authorization:
https://api.mobipace.com:444/v4/Authorize
Server accepting requests in JSON format by using POST method.
Parameters expected in the authorization request:
| Parameter | Type | Description | Mandatory |
|---|---|---|---|
| Username | string | Username in MOBIPACE system | YES |
| Password | string | Password in MOBIPACE system | YES |
MOBIPACE system responce:
| Parameter | Type | Description |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| SessionId | string | Session ID assigned to Partner upon successful authorization |
Method designed to send SMS messages to the MOBIPACE server.
You must first authorize on the MOBIPACE server to be able to send messages.
Within a single request, SMS messages can be sent to no more than 20 000 recipients.
URL for sending SMS messages:
Server accepting requests in JSON format by using POST method.
Parameters expected in request for sending SMS messages:
Structure of collection[Message]:
MOBIPACE system responce:
JSON request example (only mandatory parameters):
JSON request example (with all parameters):
Server responce example:
You must first authorize on the MOBIPACE server to be able to send messages.
Within a single request, SMS messages can be sent to no more than 20 000 recipients.
URL for sending SMS messages:
https://api.mobipace.com:444/v4/SendSMS
Server accepting requests in JSON format by using POST method.
Parameters expected in request for sending SMS messages:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| SessionId | string | Session ID assigned to Partner upon successful authorization | YES |
| Sender | string | SenderName from which recipient will receive message (SenderName must agreed and accepted by your account manager) |
YES |
| ScheduledDate | string | Message sending date and time. Date and time format: “yyyy-MM-dd HH:mm:ss” | NO |
| SendWithinHours | integer | Message sending speed. Message sending will be handled within specified time. Allowed valies 1-6 (hours) | NO |
| Messages | collection[Message] | Messages array to send | YES |
Structure of collection[Message]:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| Recipient | string | Recipient’s mobile number in international format without “+” or “00” | YES |
| Body | string | Message text (max. 500 symbols) | YES |
| Reference | uniqueidentifier | Unique ID of message assigned by your system. Used to tracking message status | NO |
MOBIPACE system responce:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| MessageCount | integer | Quantity of accepted messages |
| PartCount | integer | Quantity of accepted messages segments |
| AveragePrice | decimal | Average billed price |
| TotalPrice | decimal | Total billed price |
Method designed to calculate cost of sending SMS messages.
This method calculates cost of sending specified quantity of SMS messages without sending.
Within a single request, can be calculated SMS messages for up to 20 000 recipients.
URL for calculate SMS messages sending cost:
Server accepting requests in JSON format by using POST method.
Parameters used in the request are identical to those which are described in the SendSMS method.
You must first authorize on the MOBIPACE server to be able to send request.
This method calculates cost of sending specified quantity of SMS messages without sending.
Within a single request, can be calculated SMS messages for up to 20 000 recipients.
URL for calculate SMS messages sending cost:
https://api.mobipace.com:444/v4/CalculateSMS
Server accepting requests in JSON format by using POST method.
Parameters used in the request are identical to those which are described in the SendSMS method.
You must first authorize on the MOBIPACE server to be able to send request.
Method designed to request account balance which is used to send SMS messages.
You must first authorize on the MOBIPACE server to be able to send request.
URL for requesting account SMS balance:
Server accepting requests in JSON format by using POST method.
Parameters expected in request for account SMS balance:
MOBIPACE system responce:
JSON request example (with all parameters):
Server responce example:
You must first authorize on the MOBIPACE server to be able to send request.
URL for requesting account SMS balance:
https://api.mobipace.com:444/v4/QuerySMSBalance
Server accepting requests in JSON format by using POST method.
Parameters expected in request for account SMS balance:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| SessionId | string | Session ID assigned to Partner upon successful authorization | YES |
MOBIPACE system responce:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| Balance | decimal | Current SMS balance |
| BalanceNegativeLimit | decimal | Credit limit for sending SMS messages |
| AvailableFunds | decimal | Available funds including credit |
Method designed to request current statuses of sent SMS messages.
Method returns all statuses of requested SMS messages which were sent within last 48 hours.
Within a single request, can be requested up to 20 000 statuses.
Important! To be able to use functionality of this method, it is required to assign unique ID to every message when submitting messages via SendSMS method. Unique IDs should be defined in Reference parameter of [Message] collection (see SendSMS method description).
URL for request current statuses of sent SMS messages:
Server accepting requests in JSON format by using POST method.
Parameters expected in request to get current statuses of sent SMS messages:
MOBIPACE system responce:
Structure of collection[MessageStatus]:
JSON request example (with all parameters):
Server responce example:
Method returns all statuses of requested SMS messages which were sent within last 48 hours.
Within a single request, can be requested up to 20 000 statuses.
Important! To be able to use functionality of this method, it is required to assign unique ID to every message when submitting messages via SendSMS method. Unique IDs should be defined in Reference parameter of [Message] collection (see SendSMS method description).
URL for request current statuses of sent SMS messages:
https://api.mobipace.com:444/v4/QuerySMSMessages
Server accepting requests in JSON format by using POST method.
Parameters expected in request to get current statuses of sent SMS messages:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| SessionId | string | Session ID assigned to Partner upon successful authorization | YES |
| References | collection[string] | Array of unique IDs assigned to SMS messages by your system | YES |
MOBIPACE system responce:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| MessageStatuses | collection[MessageStatus] | Array of requested SMS messages statuses |
Structure of collection[MessageStatus]:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| Reference | string | Unique ID assigned to SMS message by your system |
| StatusCode | string | Message status code |
| Status | string | Text value of the message status |
Method designed to send VIBER messages to the MOBIPACE server.
You must first authorize on the MOBIPACE server to be able to send messages.
Within a single request, VIBER messages can be sent to no more than 100 000 recipients.
URL for sending VIBER messages:
Server accepting requests in JSON format by using POST method.
Parameters expected in request for sending VIBER messages:
Structure of collection[ViberMessage]:
MOBIPACE system responce:
JSON request example (only mandatory parameters):
JSON request example (with all parameters):
Server responce example:
You must first authorize on the MOBIPACE server to be able to send messages.
Within a single request, VIBER messages can be sent to no more than 100 000 recipients.
URL for sending VIBER messages:
https://api.mobipace.com:444/v4/SendViber
Server accepting requests in JSON format by using POST method.
Parameters expected in request for sending VIBER messages:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| SessionId | string | Session ID assigned to Partner upon successful authorization | YES |
| Sender | string | VIBER SenderName from which recipient will receive message (SenderName must agreed and accepted by your account manager) |
YES |
| ScheduledDate | string | Message sending date and time. Date and time format: “yyyy-MM-dd HH:mm:ss” | NO |
| SendWithinHours | integer | Parameter used for limiting message sending speed. Message sending will be distributed for the time specified in parameter. Allowed values 0-6 (hours). 0 means no limit. | NO |
| ViberMessages | collection[ViberMessage] | Messages array to send | YES |
| ValidityPeriod | integer | Message sending and status update livetime. System will try to deliver message and update statuses within specified period. Allowed values 10-1440 (minutes) | YES |
Structure of collection[ViberMessage]:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| Recipient | string | Recipient’s mobile number in international format without “+” or “00” | YES |
| Body | string | Message text (max. 1000 symbols) | YES |
| Reference | uniqueidentifier | Unique ID of message assigned by your system. Used to tracking message status | NO |
| Caption | string | Button text for going to the Partner's website | NO |
| Action | URL | Link to the Partner's website to which the recipient goes when clicking on the button | NO |
| Image | URL | Message image URL | NO |
MOBIPACE system responce:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| MessageCount | integer | Quantity of submitted messages |
| ValidMessagesCount | integer | Quantity of accepted messages |
| AveragePrice | decimal | Average billed price |
| TotalPrice | decimal | Total billed price |
Method designed to calculate cost of sending VIBER messages.
This method calculates cost of sending specified quantity of VIBER messages without sending.
Within a single request, can be calculated SMS messages for up to 100 000 recipients.
URL for calculate VIBER messages sending cost:
Server accepting requests in JSON format by using POST method.
Parameters used in the request are identical to those which are described in the SendViber method.
You must first authorize on the MOBIPACE server to be able to send request.
This method calculates cost of sending specified quantity of VIBER messages without sending.
Within a single request, can be calculated SMS messages for up to 100 000 recipients.
URL for calculate VIBER messages sending cost:
https://api.mobipace.com:444/v4/CalculateViber
Server accepting requests in JSON format by using POST method.
Parameters used in the request are identical to those which are described in the SendViber method.
You must first authorize on the MOBIPACE server to be able to send request.
Method designed to request account balance which is used to send VIBER messages.
You must first authorize on the MOBIPACE server to be able to send request.
URL for requesting account VIBER balance:
Server accepting requests in JSON format by using POST method.
Parameters expected in request for account VIBER balance:
MOBIPACE system responce:
JSON request example (with all parameters):
Server responce example:
You must first authorize on the MOBIPACE server to be able to send request.
URL for requesting account VIBER balance:
https://api.mobipace.com:444/v4/QueryViberBalance
Server accepting requests in JSON format by using POST method.
Parameters expected in request for account VIBER balance:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| SessionId | string | Session ID assigned to Partner upon successful authorization | YES |
MOBIPACE system responce:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| Balance | decimal | Current VIBER balance |
| BalanceNegativeLimit | decimal | Credit limit for sending VIBER messages |
| AvailableFunds | decimal | Available funds including credit |
Method designed to request current statuses of sent VIBER messages.
Method returns all statuses of requested VIBER messages which were sent within last 48 hours.
Within a single request, can be requested up to 20 000 statuses.
Important! To be able to use functionality of this method, it is required to assign unique ID to every message when submitting messages via SendViber method. Unique IDs should be defined in Reference parameter of [ViberMessage] collection (see SendViber method description).
URL for request current statuses of sent VIBER messages:
Server accepting requests in JSON format by using POST method.
Parameters expected in request to get current statuses of sent VIBER messages:
MOBIPACE system responce:
Structure of collection[MessageStatus]:
JSON request example (with all parameters):
Server responce example:
Method returns all statuses of requested VIBER messages which were sent within last 48 hours.
Within a single request, can be requested up to 20 000 statuses.
Important! To be able to use functionality of this method, it is required to assign unique ID to every message when submitting messages via SendViber method. Unique IDs should be defined in Reference parameter of [ViberMessage] collection (see SendViber method description).
URL for request current statuses of sent VIBER messages:
https://api.mobipace.com:444/v4/QueryViberMessages
Server accepting requests in JSON format by using POST method.
Parameters expected in request to get current statuses of sent VIBER messages:
| PARAMETER | TYPE | DESCRIPTION | MANDATORY |
|---|---|---|---|
| SessionId | string | Session ID assigned to Partner upon successful authorization | YES |
| References | collection[string] | Array of unique IDs assigned to SMS messages by your system | YES |
MOBIPACE system responce:
| PARAMETER | TYPE | DESCRIPTION |
|---|---|---|
| StatusCode | integer | Request processing status code |
| Status | string | Text value of the request processing status code |
| MessageStatuses | collection[MessageStatus] | Array of requested SMS messages statuses |
Structure of collection[MessageStatus]:
| PARAMETER | TYPE | DESCRIPTION | ALWAYS PRESENT |
|---|---|---|---|
| Reference | string | Unique ID assigned to SMS message by your system | YES |
| StatusCode | string | Message status code | YES |
| Status | string | Text value of the message status | YES |
| DeliveryDate | string | Message Delivery Date in Unix Time format | NO |
| SeenDate | string | Message Opened/Seen Date in Unix Time format | NO |
Message Status possible values
| Code | Value | Description | State |
|---|---|---|---|
| 1 | Pending | Message is being prepared for sending | Intermediate |
| 2 | Scheduled | Message scheduled and queued for sending | Intermediate |
| 3 | Sent | Message Sent | Intermediate |
| 4 | OutOfBalance | Not enough funds to send messages | Final |
| 5 | InvalidMobile | Invalid mobile number | Final |
| 6 | InvalidBody | Message body symbols count exceed. You can send SMS message which contains up to 500 symbols and VIBER messages which contains up to 1000 symbols | Final |
| 7 | InvalidRoute | Destination not available for your account. Contact your account manager | Final |
| 8 | BlockedMobile | Mobile number blocked for delivery. The recipient added his number to Black list (refused to receive messages) | Final |
| 9 | Unknown | Message with specified reference not found | Final |
| 10 | InvalidMarketingTime | There is restriction applied in System. Sending SMS messages from registered advertising sender names to Armenian mobile subscribers is only possible between Monday and Friday from 10:00 to 20:00 (UTC+4) | Final |
| 20 | InvalidImageURL | Incorrect value for parameter Image. Message was not sent (only for VIBER messages) |
Final |
| 21 | ActionNotDefined | Caption parameter value defined, but Action parameter value missing. Message was not sent (only for VIBER messages) |
Final |
| 22 | CaptionNotDefined | Action parameter value defined, but Caption parameter value missing. Message was not sent (only for VIBER messages) |
Final |
| 23 | InvalidActionURL | Incorrect value for parameter Action . Message was not sent (only for VIBER messages) |
Final |
| 24 | InvalidSite | Site mentioned in Action parameter is unreachable. Message was not sent (only for VIBER messages) |
Final |
| 25 | NoImageFound | Link mentiond in Image paramenter must return only image. Message was not sent (only for VIBER messages) |
Final |
| 26 | CaptionAndActionMustDefined | If you are using Image parameter Caption and Action parameters must be defined. Message was not sent (only for VIBER messages) |
Final |
| 100 | Delivered | Message delivered to recipient | Final |
| 101 | Undeliverable | Message not delivered | Final |
| 102 | Expired | Message sent, but message status unknown | Final |
| 103 | RejectedByOperator | Message rejected by operator | Final |
| 104 | TimeOut | System error. Message processing timeout reached. Message was not sent | Final |
| 105 | Seen | Message opened by recipient. System monitors this status during specified ValidityPeriod (refer to SendViber method). (only for VIBER messages) |
Final |
| 106 | NotSeen | Message not opened by recipient yet. System monitors this status during specified ValidityPeriod (refer to SendViber method). (only for VIBER messages) |
Intermediate |
| 107 | NotViberUser | Recipient is not registered as VIBER user. (only for VIBER messages) |
Final |
| 108 | NoSuitableDevice | Recipient is registered as VIBER user, but device is not suitable for VIBER messages delivery (only for VIBER messages) |
Final |
Request processing status codes
| Code | Value | Description |
|---|---|---|
| 100 | Unknown | System generic error |
| 101 | Success | Request successfully completed |
| 102 | IncorrectSessionID | Incorrect format of SessionId parameter or the SessionId not provided |
| 103 | SessionExpired | Session with provided ID expired or not exists |
| 104 | AccessDenied | System currently processing another request with same Session ID. Request with this session ID is temporarly impossible. |
| 105 | IncorrectReferences | Incorrect format of References or References not provided |
| 106 | IncorrectParameter | Incorrect parameter found in request body. Please check request body |
| 200 | IncorrectUserNameOrPassword | Invalid Username or Password |
| 201 | UserLocked | Allowable mistakes count during authorization reached to maximum. Please try again in 30 minutes. |
| 202 | UserBlocked | Account blocked by administrator. Contact your account manager |
| 300 | OutOfBalance | Not enough funds to send messages |
| 301 | CountOverflow | MOBIPACE allows to send/check statuses for up to 20 000 SMS messages and send/check statuses up to 100 000/20 000 VIBER messages within one request |
| 302 | CurrencyNotDefined | Account currency is not defined. Go to “Profile” section and define your account currency |
| 303 | SenderNotDefined | Sender parameter value is missing |
| 304 | MessagesNotDefined | Request does not contain any message to send |
| 305 | InvalidSenderName | Sender Name not registered. Contact your account manager. |
| 306 | InvalidDateTimeFormat | Invalid format of ScheduledDate parameter. Valid format is "yyyy-MM-dd HH:mm:ss". |
| 307 | PastDateTime | ScheduledDate parameter value set in past. |
| 308 | InvalidSendWithinHours | Incorrect value of SendWithinHours parameter. Value should be within 1 - 6 (hours). |
| 309 | IncorrectValidityPeriod | Incorrect value of ValidityPeriod parameter. Value should be within 10 - 1440 (minutes). (only for VIBER messages) |
| 310 | NoValidMessages | System did not found any valid message to send. If used SendSMS/SendViber please check message statuses in Statistics page or use QuerySMSMessages/QueryViberMessages methods. |
| 311 | InvalidMarketingTime | There is restriction applied in system. Sending SMS messages from registered advertising sender names to Armenian mobile subscribers is only possible between Monday and Friday from 10:00 to 20:00 (UTC+4) |
| 312 | ViberChannelNotActivated | VIBER channel not activated by administrator. Contact your account manager |
Exclusive rights notice
The MOBIPACE system (as well as the copyright holder specified by it) has exclusive rights to all the results of intellectual activity and subsequent individualization used in development, support and using of HTTP API 4.0 product.
Mentioned results may include computer programs, databases, images, texts, other works, as well as inventions, utility models, trademarks, service marks, commercial designations and brand names.
These rights are protected in accordance with the Civil Code of the Russian Federation and International law.
You can use the HTTP API 4.0 product of the MOBIPACE system or its component parts only within the authority granted to you by the User agreement or special agreement.
Violation of the requirements for the protection of exclusive rights of the copyright holder entails disciplinary, civil, administrative or criminal liability in accordance with International and Russian legislation.
The MOBIPACE system (as well as the copyright holder specified by it) has exclusive rights to all the results of intellectual activity and subsequent individualization used in development, support and using of HTTP API 4.0 product.
Mentioned results may include computer programs, databases, images, texts, other works, as well as inventions, utility models, trademarks, service marks, commercial designations and brand names.
These rights are protected in accordance with the Civil Code of the Russian Federation and International law.
You can use the HTTP API 4.0 product of the MOBIPACE system or its component parts only within the authority granted to you by the User agreement or special agreement.
Violation of the requirements for the protection of exclusive rights of the copyright holder entails disciplinary, civil, administrative or criminal liability in accordance with International and Russian legislation.
Changes in HTTP API 4.0 of the MOBIPACE system
1. MOBIPACE reserves the right to make changes to the HTTP API 4.0 functionality
2. Partner’s software should interact with MOBIPACE without errors, in case of new restrictions. The appearance of new restrictions should not cause malfunction of the Partner’s software and/or errors in the server responses interpretation.
3. MOBIPACE will inform the Partners about the changes and publish corresponding information on the website at least 14 days before changes take effect. During this period, the Partner have to make the necessary changes in his software and verify its functionality.
4. If changes will result to malfunctions in the Partner’s software and the corresponding changes cannot be performed until the deadline, the Partner’s responsible person should contact MOBIPACE technical support team.
5. MOBIPACE management team can postpone the deadlines in case of necessity.
6. Information about changes published on the www.mobipace.com should be regularly reviewed by the Partner.
1. MOBIPACE reserves the right to make changes to the HTTP API 4.0 functionality
2. Partner’s software should interact with MOBIPACE without errors, in case of new restrictions. The appearance of new restrictions should not cause malfunction of the Partner’s software and/or errors in the server responses interpretation.
3. MOBIPACE will inform the Partners about the changes and publish corresponding information on the website at least 14 days before changes take effect. During this period, the Partner have to make the necessary changes in his software and verify its functionality.
4. If changes will result to malfunctions in the Partner’s software and the corresponding changes cannot be performed until the deadline, the Partner’s responsible person should contact MOBIPACE technical support team.
5. MOBIPACE management team can postpone the deadlines in case of necessity.
6. Information about changes published on the www.mobipace.com should be regularly reviewed by the Partner.