General Guidelines

1. Successful results should return “Response.TransStatus” as “false”.
2. Unsuccessful results should return “Response.TransStatus” as “true” and corresponding error message in “Response.TransRemarks”.
3. Connectors should collect provider credentials in service requests.
4. Connector should validate the Channel Code received in the request and should respond only to the designated ChannelCode.
5. Connectors will have a designated Currency and if currency conversion is required, will be handled by WebConnect.
6. Connector need to handle Fare Rules, Baggage and Meals only if they are provided by Airline API, otherwise Web Connect will handle it.
7. Connector will be sending all amounts in Connectors Designated currency only and Web Connect should send the same amount and currency in the following requests.
8. Departure/Arrival Date and Time should be in Local Date and Time of the Departure/Arrival Airport
9. Connector Settings should be implemented as Singleton.
10. Any table used in Connector should be placed in Connector Main DB.
11. Separate API layer for Docker should be implemented.
12. Connector should work both in docker and dll models (Should be switchable).
13. All requests and response payloads of all Provider API calls should be logged. Enabling
of logging should be configurable.