PT.Api

<back to all web services

GetDepartureSettingByApp

The following routes are available for this service:
GET/api/getdeparturesettingbyapp
POST/api/getdeparturesettingbyapp
GetDepartureSettingByApp Parameters:
NameParameterData TypeRequiredDescription
ClientAppbodystringNo
BaseRequest Parameters:
NameParameterData TypeRequiredDescription
VersionformintNoVersion. Ex: 1,2,3,...
GetDepartureSettingByAppResponse Parameters:
NameParameterData TypeRequiredDescription
Dataformtbl_DepartureNo
BaseResponse Parameters:
NameParameterData TypeRequiredDescription
StatusformintNoResponse status. Ex: 1 - Success; 0 - Error
MessageformstringNoResponse message
tbl_Departure Parameters:
NameParameterData TypeRequiredDescription
ValidStartDateformDateTimeNo
ValidEndDateformDateTimeNo
ValidStartDateOffsetformintNo
MaxBookSeatformintNo
EmailTemplateNameformstringNo
SMSTemplateNameformstringNo
PrePaidEmailTemplateNameformstringNo
PrePaidSMSTemplateNameformstringNo
ReturnSuccessUrlFormatformstringNo
ReturnErrorUrlFormatformstringNo
AppformstringNo
MetaformstringNo

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/GetDepartureSettingByApp HTTP/1.1 
Host: api4.futabus.vn 
Content-Type: application/json
Content-Length: length

{"ClientApp":"String","Version":0}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"Data":{"ValidStartDateOffset":0,"MaxBookSeat":0,"EmailTemplateName":"String","SMSTemplateName":"String","PrePaidEmailTemplateName":"String","PrePaidSMSTemplateName":"String","ReturnSuccessUrlFormat":"String","ReturnErrorUrlFormat":"String","App":"String","Meta":"String"},"Status":0,"Message":"String"}