The plugin has the ability to use the Travelgenix API in the TripAppy plugin as a data source, replacing the Traveltek API.

Maintains ease of use of the interface and feature set. The idea is to have a flag in the WordPress site’s environment variable set that tells the TripAppy plugin which data source to pull the data from. Preserves classes as they are bound to database tables within the TripAppy plugin rather than directly to the Traveltek API.

The two APIs have completely different calling approaches: the Traveltek API runs synchronously, whereas the Travelgenix API runs asynchronously. Gives a quick initial response to create a search and then polls the results, checking the flags it has completed. Once complete, the results are stored as they are available from the Travelgenix API without waiting for processing to complete.