Stay organized with collections
Save and categorize content based on your preferences.
Request
ListBookingsRequest
Return value
ListBookingsResponse
This only needs to return future bookings for a user, not bookings for all time.
Canonical gRPC error codes
NOT_FOUND (if the requested user ID is unknown to the partner)
// Request to list all upcoming bookings for a usermessageListBookingsRequest{// ID of the user (required)stringuser_id=1;}// Response for the [ext.maps.booking.partner.v2.ListBookings] RPC with all// upcoming bookings for the requested usermessageListBookingsResponse{// All bookings of the user (required)repeatedBookingbookings=1;}
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-10-31 UTC."],[[["The `ListBookings` RPC retrieves upcoming bookings for a specific user."],["Requests must include the user's ID and will return a `NOT_FOUND` error if the ID is unknown."],["The response contains a list of `Booking` objects representing the user's future bookings."]]],["The `ListBookingsRequest` requires a `user_id` to retrieve a user's future bookings. The `ListBookingsResponse` returns a list of `bookings` for the specified user. The system should only return future bookings, not historical ones. If the provided `user_id` is not found, the service will respond with a `NOT_FOUND` gRPC error code. The request is made through the `ListBookings` RPC.\n"]]