Setting up new connections

Owned by Vishal Waghmare
Mar 07, 2024
2 min read

 

Introduction: Setting up new API connections involves integrating different software systems to communicate seamlessly, enabling data exchange and functionality across applications. This introductory process typically includes identifying the API endpoints, obtaining authentication credentials, configuring access permissions, and testing connectivity to ensure smooth interaction between systems.

 

There are basically two type of connections setup that are used by clients:

  • Soap Connection (Web service user)

We usually don't provide access to the soap anymore because it's obsolete and replaced by the rest API.

 At some moment the soap API will be turned off and all applications need to move to the rest API.

 There is no date for this yet. We only maintain the soap API for critical bugs and not add any new features.

 Below are the steps in order to provide the credentials to setup the soap connection :

Example for DC : Bunglowspecials

1)Confirm the costs for the connection + special Pricecache €695

There are costs involved for a new connection, it's € 395,00. In case Bunglowspecials need exclusive offers, we need to set up a new price cache which will cost EUR 300.

2)Fill in the DC sheet.

3)Create respective DC.

4)Link the new DC to the mentioned accommodations.

5)Create employee for Bungalow Specials on that concern.

6)Send the factsheet to Bungalow Specials so they can start setting up the connection.

7)Wait for the confirmation from Bungalow Specials that it's working fine.

WEBSERVICE URL’s for SOAP : https://maxxton.atlassian.net/wiki/spaces/OWC/pages/11404059/Webservice+URL+s

 

  • REST API Connection (API USER):

  1. Check if there is a DC existing. If not , then create a DC.

  2. Then create a new API user which is valid for that specific DC and RC.

 Please refer https://maxxton.atlassian.net/wiki/spaces/DEV/pages/239534085

 The API user does have a possibility to  link RC and DC. The functional behaviour is as follows:

 DC :

  • If nothing is linked then it is applicable to all DC's. So in the request body it is mandatory for the user to pass a DC code/Id. 

  • If a specific DC is linked then there is no need to pass DC code/Id in the request body and response returned is only as per the DC linked with API user.

  • In other words an API user having a DC linked should have access only to that data applicable for that DC.

  RC :

  • If nothing is linked then it is applicable to all RC's. So in the request body it is mandatory for the user to pass a RC code/Id.  

  • If a specific RC is linked then there is no need to pass RC code/Id in the request body and response returned is only as per the RC linked with API user.

  • In other words an API user having a RC linked should have access only to that data applicable for that RC.

 

API COSTS :

The API costs are based on the number of requests per month, the first 750,000 requests per month(25,000 requests per day) are not charged. Subsequent requests are charged as per the API price calculator.
Refer below API pricing calculator :  

 Also for rest API, do refer our swagger documentation link : 

Also refer documentation for Pricecache :