Cochrane+ App API

EndJourney

The following routes are available for this service:
POST	/journey/end

**EndJourney** Parameters:
Name	Parameter	Data Type	Required	Description
JourneyId	body	int	No

**ApiServiceRequest** Parameters:
Name	Parameter	Data Type	Required	Description
ApiKey	form	string	Yes	The API Key required for authentication
Latitude	form	double	No	Latitude of the user making this request
Longitude	form	double	No	Longitude of the user making this request

**EndJourneyResponse** Parameters:
Name	Parameter	Data Type	Required	Description
Journey	form	JourneyData	No

**ApiServiceResponse** Parameters:
Name	Parameter	Data Type	Required
Description	form	string	No
Heading	form	string	No
WasSuccessful	form	bool	No
ModelState	form	Object	No

**JourneyData** Parameters:
Name	Parameter	Data Type	Required
JourneyId	form	int	No
Title	form	string	No
StartTime	form	string	No
EndTime	form	string	No
Distance	form	double	No
DistanceFormatted	form	string	No
RoutePolyline	form	string	No
StartPoint	form	JourneyPointData	No
EndPoint	form	JourneyPointData	No
MeetingData	form	MeetingData	No
JourneyNotes	form	List<JourneyNoteData>	No

**JourneyPointData** Parameters:
Name	Parameter	Data Type	Required
Latitude	form	double	No
Longitude	form	double	No
Address	form	string	No

**MeetingData** Parameters:
Name	Parameter	Data Type	Required
MeetingId	form	int	No
StartTime	form	string	No
ArrivalTime	form	string	No
LeftTime	form	string	No
Duration	form	string	No
ShowTimeFields	form	bool	No
ArrivalStatus	form	string	No
Email	form	string	No
HasEmail	form	bool	No
ContactName	form	string	No
Latitude	form	double	No
Longitude	form	double	No
Location	form	string	No
Address	form	string	No
Subject	form	string	No
Description	form	string	No
EndTime	form	string	No
Company	form	string	No
ContactNumber	form	string	No
HasContactNumber	form	bool	No
HasLocation	form	bool	No
SetBy	form	string	No
VirtualOrInPerson	form	string	No

**JourneyNoteData** Parameters:
Name	Parameter	Data Type	Required	Description
Note	form	string	No
Date	form	string	No

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 /journey/end HTTP/1.1 
Host: cochraneplus-api-dev.happen.zone 
Accept: text/jsv
Content-Type: text/jsv
Content-Length: length

{
	journeyId: 0,
	apiKey: String,
	latitude: 0,
	longitude: 0
}

HTTP/1.1 200 OK
Content-Type: text/jsv
Content-Length: length

{
	description: String,
	heading: String,
	wasSuccessful: False,
	modelState: {}
}