| commit | bd3a9ea7ad4bdf65c6cea8c838f7fa738cc36c0c | [log] [tgz] |
|---|---|---|
| author | Yunsi Mou <yunsi@yunsi.hot.corp.google.com> | Tue Feb 27 12:57:25 2018 -0500 |
| committer | Yunsi Mou <yunsi@yunsi.hot.corp.google.com> | Tue Feb 27 12:57:25 2018 -0500 |
| tree | f874ff000fccffe44e091bed83f48f576ac1fe6a | |
| parent | c9b6477ba4cd0985d4a3713633f67ea4efa9480b [diff] |
add command for retrieving the code example
Have your service account created, download your private key.
Download the Java client library , unzip the file to get the ‘mapsbooking’ package.
Create a java project in your IDE, retrieve the sample codes (InventoryUpdate.java & BookingNotification.java) from this repo:
git clone https://maps-booking.googlesource.com/java-maps-booking-api-example
import them into your java project under src directory.
Make a copy of your private key (JSON file) to the src directory.
Add the Java Client Library to the dependencies of your project (include jar files under mapsbooking and libs-sources directory).
In both java files, follow the TODOs to complete your implementations.
More detail about the REST API can be found here.
Create a merchant/service with existing merchantId/serviceId, your will get following error message: 409 Conflict { “code” : 409, “errors” : [ { “domain” : “global”, “message” : “Requested entity already exists”, “reason” : “alreadyExists”, “debugInfo” : “detail: "[ORIGINAL ERROR] generic::already_exists: ...”\n" } ], “message” : “Requested entity already exists”, “status” : “ALREADY_EXISTS” }
Update/Delete with wrong merchantId/serviceId (update with wrong bookingId), your will get following error message: 404 Not Found { “code” : 404, “errors” : [ { “domain” : “global”, “message” : “Requested entity was not found.”, “reason” : “notFound”, “debugInfo” : “detail: "[ORIGINAL ERROR] spanner::Row not found:..."\n” } ], “message” : “Requested entity was not found.”, “status” : “NOT_FOUND” }
In all update functions, the parameter ‘updateMask’ must be in FieldMask format to specify the fields to update. The API is required to only change the values of the fields as specified in the mask and leave the others untouched. If you pass the wrong updateMask string, the update will not take effect. If a field mask is not present on update, the operation applies to all fields (as if a field mask of all fields has been specified). So if you want to update all fields, just set the updateMask empty.
Since an Availability Slot is not associated with a merchant_id/service_id, if you make the replace availability calls with invalid merchant_id/service_id, you will be able to make the REST call without any issue, but your request will not be served in the production due to the invalid merchant_id/service_id.
Any field that has a zero value is not shown in the response.