PT.Api

<back to all web services

QueryBoardingPoint

The following routes are available for this service:
POST/api/queryboardingpoint
QueryBoardingPoint Parameters:
NameParameterData TypeRequiredDescription
RouteIdbodyintYes
DepartureTimebodystringYesHH:mm
DepartureDatebodystringYesHH:mm
WayIdbodyintNo
LocaleRequest Parameters:
NameParameterData TypeRequiredDescription
LocaleformstringNoLocale. Ex: vi-VN, en-US
BaseRequest Parameters:
NameParameterData TypeRequiredDescription
VersionformintNoVersion. Ex: 1,2,3,...
QueryBoardingPointResponse Parameters:
NameParameterData TypeRequiredDescription
DataformList<BoardingPoint>No
BaseResponse Parameters:
NameParameterData TypeRequiredDescription
StatusformintNoResponse status. Ex: 1 - Success; 0 - Error
MessageformstringNoResponse message
BoardingPoint Parameters:
NameParameterData TypeRequiredDescription
IdformintNo
TypeformintNo
NameformstringNo
AddressformstringNo
PhoneformstringNo
LatitudeformfloatNo
LongitudeformfloatNo
DistanceformintNo
DurationformintNo
OfficeIdformintNo

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

HTTP + JSV

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

POST /jsv/reply/QueryBoardingPoint HTTP/1.1 
Host: api.futabus.vn 
Content-Type: text/jsv
Content-Length: length

{
	RouteId: 0,
	DepartureTime: String,
	DepartureDate: String,
	WayId: 0,
	Locale: vi-VN,
	Version: 0
}
HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	Data: 
	[
		{
			Id: 0,
			Type: 0,
			Name: String,
			Address: String,
			Phone: String,
			Latitude: 0,
			Longitude: 0,
			Distance: 0,
			Duration: 0,
			OfficeId: 0
		}
	],
	Status: 0,
	Message: String
}