(1)
Because testing and production environment are different you can test in this url, testing flights:
Production
http://www.volaris.com.mx/

Testing
http://200.79.47.238:8002/

 (2)  
All agency has an additional booking fee and some fare only available for direct clients not for agencies

(3)
In testing environment only AMEX works, in production all work (but we don’t have testing cards for production) You can use yours but talk to Rodrigo about the refund before you use them.

Thank and best regards.

Note:
Urls for Volaris Web Services
       PRODUCTION: (
          http://200.79.47.238:8082/VOLARISWS/Consulta.asmx
          http://200.79.47.238:8082/VOLARISWS/Operacion.asmx

       TESTING:
          http://200.79.47.238:8081/VOLARISWS/Consulta.asmx
          http://200.79.47.238:8081/VOLARISWS/Operacion.asmx

Eric Gutiérrez
Internet y comercio electrónico ▪  IT
t: (55)  5261  6400 ▪ ext.6570
volaris.com.mx       01 800 122 8000

Reduce, Reusa y Recicla por un Cielo Azul
PAntes de imprimir este mensaje, asegúrese de que es necesario.
El medio ambiente está en nuestras manos

From: Travelfusion Flight [mailto:flight@travelfusion.com]
Sent: Jueves, 13 de Mayo de 2010 12:34 a.m.
To: Eric Gutierrez Cruz
Cc: newsupp; Rodrigo Fernandez Labastida; Nancy Adriana Hernandez Zepeda; flight@travelfusion.com
Subject: Re: [NEWSUPP-416][Volaris]Questions about the API

Dear Eric,

(1) In the screen print, we see there are 2 direct flights and 3 connection flights, you said the webservice can not differentiate the stop flights like 153/132 and 153/134. Then what about those 2 direct flights? They should have been displayed in XML response, but as we have mentioned in the previous letter we got only one direct flight result there.(check the attachment please)
(2) Regarding the cost, do you mean the price from XML response will be different from the one on website even we login with the same user and password?
(3) About the test card you provided, American Express works fine, but we got New payments associated with the booking did not pass validation as we used the VISA and Master Card.

Looking forward to hearing from you soon.

On Wed, May 12, 2010 at 11:44 PM, Eric Gutierrez Cruz <eric.gutierrez@volaris.com.mx> wrote:
Hi Jack,

Yes of course,
Here are the answers:

(1)
The webService don’t know the difference between a direct, stop, or connection flights
For example the flight GDL-CUN only show 153 flight that web display like (153/5130)
The web service can´t display 153/132 and 153/134 because are stop flights

(2)
Yes the cost are different. You need to login in the webpage with the same user and password and review the BreakDown.

(3)
The test card are:
American Express           378282246310005            (15) Characters
Master Card      5105105105105100          (16) Characters
Visa       4111111111111111          (16) Characters

Regards

Eric Gutiérrez
Internet y comercio electrónico ▪  IT
t: (55)  5261  6400 ▪ ext.6570
volaris.com.mx       01 800 122 8000

Reduce, Reusa y Recicla por un Cielo Azul
PAntes de imprimir este mensaje, asegúrese de que es necesario.
El medio ambiente está en nuestras manos

From: Travelfusion Flight [mailto:flight@travelfusion.com]
Sent: Miércoles, 12 de Mayo de 2010 02:01 a.m.
To: Eric Gutierrez Cruz
Cc: newsupp; flight@travelfusion.com; Rodrigo Fernandez Labastida; Toney Javier Roa Cabana
Subject: [NEWSUPP-416][Volaris]Questions about the API

Dear Eric,

Let's open a new page for this issue, please reply us here.

Here are the couple of new questions, please kindly clarify the following points for us:
(1) For the criteria: CUN—>GDL outwarddate：2010-05-13 returndate：2010-05-14,  there are 2 outward results and 5 return results on website, but we found there are only 1 outward and 1 return result in the response of fGetAvailabilityByTripXML. (Screenprint request and response attached).

(2) Price mismatch issue. For the case above, in the search response, the outward price is 962 MXN and the return price is 982 MXN, also in the response we got "VClases= J Siguiente clase = J"(want to save), but on website, choosing for 'want to save' flight(631, 630) are not available.
Moreover, for CUN—>MTY outwarddate：2010-05-13 returndate：2010-05-14, the outward total price 2577 MXN and return is 2588 MXN, but on website the price was given with 2544 MXN and 2719 MXN respectively.

(3) We got an exception as we call fBookingXML: New payments associated with the booking did not pass validation (request and response attached), was it due to the 'invalid card details'? We need to confirm that we can get the related 'error message' for such case. Also, as we are working on it in test environment, could you please provide us with a TEST card?

Your prompt reply would help us greatly.

Regards,

AVISO DE CONFIDENCIALIDAD:
La información contenida es para uso de la persona a la que se le ha enviado, y esta protegida por las leyes y tratados respectivos. Este correo electrónico no debe ser considerado como constitutivo de ninguna relación legal o contractual.

NOTICE OF CONFIDENTIALITY:
The information transmitted is intended only for the person to which it is addressed and may contain information duly protected by the law. This e-mail is not, and should not be considered as, the basis of any legal or contractual relationship.



--
TravelFusion, Flight Team