This section will introduce you to all the information that you are going to need in order to start your integration. You will be given access to all the resources detailed in this section as soon as your registration has been completed.

Test environment endpoint: 
http://www.stubademo.com/RXLStagingServices/ASMX/XmlService.asmx

Live environment endpoint:
http://api.stuba.com/RXLServices/ASMX/XmlService.asmx
(This is a default URL. An alternative URL may be provided alongside your live credentials, and you should always use the URL provided)

Agency details:
Login details for an agency user – these have 2 parts: an AuthApiKey and IP address .

AuthApiKey: <AuthApiKey>

IP address

To communicate with the Stuba API Service, use an HTTP POST request.  The JSON payload should be sent in the body, while the authentication key (AuthApiKey) must be included in the header.

POST https://example.com/ [Endpoint]

Headers:

Content-Type: application/json

AuthApiKey: <Your AuthApiKey>

Accept-Encoding: gzip,br

Body:

{JSON payload}

[Endpoint] – Replace with the specific API operation you are calling (e.g., Region Search, Hotel Search, etc.).

AuthApiKey – Your unique API key, provided by Stuba.

Content-Type – Must be set to application/json.

Body – Should contain a properly structured JSON request.

The Stuba API Service Interface supports HTTP 1.1 compression.

Clients must take advantage of compression by ensuring that requests to the interface specify the HTTP header: Accept-Encoding: gzip, deflate If this is specified on any request, then the corresponding response will be returned in a compressed format.

We recommend that this header is specified for all requests as it can offer a significant performance improvement, especially for large availability searches.