Skip to main content

SoftConEx Connector

Product Management avatar
Written by Product Management
Updated this week

Overview

This article presents an overview of Nezasa's SoftConEx connector, exploring its main use cases. The SoftConEx Travel API for flights offers flight-related data and services integration.

TripBuilder seamlessly integrates with SoftConEx Travel API, granting clients effortless access to the extensive range of flight options offered through SoftConEx’s connector.

Supported Use Cases via API

Use Case

Support Description

Search Offers

Supported

Get Offer Details

Supported

Availability Check

Supported

Book

Supported

Cancel

Supported (only possible before ticketing and applicable to just some airlines)

Booking Change

Not supported via API

(Users will need to conduct the change in an external system and then reimport the PNR in TripBuilder to update some of the fields as part of the booking change)

Name Change

Not supported via API

(Users will need to conduct the change in an external system and then reimport the PNR in TripBuilder to update some of the fields as part of the booking change)

Cancellation Policies

Not supported

Offer Terms & Conditions (i.e. Fare Rules)

Supported

Setting up new credentials

To establish SoftConEx credentials, you'll need relevant details from the supplier, including Access Key, Login Name, Login Password and Server. Please contact our support team or your customer success manager for more info or consult your SoftConEx pier for better understanding.

Testing

Unfortunately, we don't have a dedicated test environment available at the moment. Currently, the test environment is designed to meet standards and is only accessible for engineering certifications.

Customers seeking testing solutions may have the option to create controlled setups to make use of available testing tools by the supplier, namely the SoftConEx sandbox. You can inquire about the potential access to this specialised test environment by reaching out to your assigned SoftConEx contact.

Did this answer your question?