Good News! You now have Mobility enabled on your project. The next step is to demonstrate that you can report a trip as billable. This is accomplished by performing the Report Billable Trips Test as outlined below. You must demonstrate to Google before product launch that you can report a trip as billable in order for Google to set up your Billing Account with per-trip billing.
Report Billable Trips Test
- Enable Local Rides and Deliveries API in Google Cloud Console. This API is available once your project has access.
- Implement ReportBillableTrip API.
- Run the test and record the following fields to a csv file. Google uses this file to validate test results. As a reminder this test runs for 48 hours and requires a minimum of 1000 trips.
- billable_trip_id
- country_code
- http_status
- error_message
- request_timestamp_utc
- response_timestamp_utc
* Timestamps should have ISO 8601 date format: YYYY-MM-DDThh:mm:ss
- Send Woolpert the csv test results. Woolpert works with Google to validate your results.
- Note that once this initial csv is validate by Google, this process does not have to be repeated in the future
- Note that once this initial csv is validate by Google, this process does not have to be repeated in the future
Implement ReportBillableTrips API
To report a trip as billable, issue an HTTP POST to the ReportBillableTrip API, in FleetEngine:
https://fleetengine.googleapis.com/v1/providers/<YOUR-PROJECT-ID>/billableTrips/<YOUR-TRIP-ID>:report?countryCode=<YOUR-COUNTRY-CODE>&key=<YOUR-API-KEY>
- YOUR-PROJECT-ID: Google Cloud project that has ODRD enabled
- YOUR-TRIP-ID: trip id unique to each billable event. See Trip ID Requirements (see requirements below)
- YOUR-COUNTRY-CODE: for a list of country codes see Google Maps Platform Coverage Details
- YOUR-API-KEY: API key associated with GMP project
The API should be called from your backend on the completion of every billable trip.
Trip ID Requirements
- Must be valid Unicode strings.
- Have a maximum length of 64 characters.
- Will be normalized according to Unicode Normalization Form C (http://www.unicode.org/reports/tr15/).
- May not contain any of the following ASCII characters: '/', ':', '\', '?', or '#'.
- May not contain any personally identifiable information
Links
If you are whitelisted for access to ODRD resources, you can get more information from the Google Developer documentation:
Comments
0 comments
Please sign in to leave a comment.