PT.Api

<back to all web services

VatoChangeTicket

The following routes are available for this service:
POST/api/vatochangeticket
VatoChangeTicket Parameters:
NameParameterData TypeRequiredDescription
MerchantIdbodyintNo5502: online, 13260: vato
CodebodystringYes
BookingIdbodyintYes
PaymentIDRefbodystringNo
PaymentResultbodystringNo
MsgbodystringNo
SeatIdsbodyIList<int>Yes
SeatNamesbodyIList<string>Yes
Code_NewbodystringYes
BookingId_NewbodyintYes
SeatIds_NewbodyIList<int>Yes
SeatNames_NewbodyIList<string>Yes
DepartureDatebodystringYesdd-MM-yyyy
DepartureTimebodystringYeshh:mm
LocaleRequest Parameters:
NameParameterData TypeRequiredDescription
LocaleformstringNoLocale. Ex: vi-VN, en-US
BaseRequest Parameters:
NameParameterData TypeRequiredDescription
VersionformintNoVersion. Ex: 1,2,3,...
BaseResponse Parameters:
NameParameterData TypeRequiredDescription
StatusformintNoResponse status. Ex: 1 - Success; 0 - Error
MessageformstringNoResponse message

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/VatoChangeTicket HTTP/1.1 
Host: api5.futabus.vn 
Content-Type: application/json
Content-Length: length

{"MerchantId":0,"Code":"String","BookingId":0,"PaymentIDRef":"String","PaymentResult":"String","Msg":"String","Code_New":"String","BookingId_New":0,"DepartureDate":"String","DepartureTime":"String","Locale":"vi-VN","Version":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Status":0,"Message":"String"}