Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update to Vehicle_Registry message #44

Merged
merged 3 commits into from
Sep 12, 2018
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions agency/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,8 +72,8 @@ Response:
This API is used by providers when a vehicle is either removed or returned to service.

Endpoint: `/update_vehicle_status`
Method: `POST`
API Key: `Required`
Method: `PUT`
API Key: `Required`
Body:

| Field | Type | Required/Optional | Other |
Expand Down Expand Up @@ -136,8 +136,8 @@ Body:
A trip represents a route taken by a provider's customer. Trip data will be reported to the API every 5 seconds while the vehicle is in motion.

Endpoint: `/update_trip_telemetry`
Method: `POST`
API Key: `Required`
Method: `POST`
API Key: `Required`
Body:

| Field | Type | Required/Optional | Other |
Expand Down Expand Up @@ -264,6 +264,6 @@ For 'message', options are:
* `305: Error: vehicle is already registered`
* `306: Error: vehicle registration cannot be found`
* `310: Error: vehicle is not properly registered`
* `311: Error: duplicate registration found, please use a different unique_id`
* `311: Error: duplicate registration found, please use a different unique_id or update existing unique_id status using the update-vehicle-status endpoint`
* `315: Error: vehicle is not active`
* `320: Error: vehicle trip has not been properly started`