Stay organized with collections
Save and categorize content based on your preferences.
Our team schedules the launch for a specific date and time. You may see a delay
of merchants going online over several hours.
Your integration is monitored for a week after the launch. If your Booking
Server or Real-Time Updates (RTUs) are over any error thresholds, we will inform
you to correct them. If the issues aren't resolved, Google will take down your
integration.
Booking Server
For all Booking Server implementations, there is a HealthCheck route that must
be included. The Actions Center periodically checks your HealthCheck route.
If it doesn't respond or returns an unhealthy response, we temporarily disable
your integration. We continue to periodically check your HealthCheck route
and after it returns a healthy response, we automatically restore your
integration.
Standard implementation methods
Error rate thresholds
Latency thresholds
CheckAvailability
Note: This booking server endpoint is legacy. New integrations must not
implement this endpoint.
<10%
<5s
BatchAvailabilityLookup
<3%
<1.5s
CreateBooking
UpdateBooking
<5%
<4s
RTUs
For RTUs, latency is measured by the time difference between when an action is
taken (for example, modifying a booking) and when Actions Center receives the
RTU request.
API
Error rate thresholds
Latency thresholds
BookingNotification RTU
<10% each day and for each state
<5 minutes
You can monitor error rates through the various Partner Portal dashboards,
namely the Feeds,
Booking Server,
and RTU
dashboards.
Inventory Compliance requirements
Make sure that you continue to follow the Inventory Compliance requirements.
For information on how a merchant can opt out of your service, see
the Remove third-party links section of
the help article.
If you violate the Inventory Compliance policy, your integration could be
disabled or terminated.
[[["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 2025-07-22 UTC."],[],[],null,["# Launch and Monitor\n\nOur team schedules the launch for a specific date and time. You may see a delay\nof merchants going online over several hours.\n\nYour integration is monitored for a week after the launch. If your Booking\nServer or Real-Time Updates (RTUs) are over any error thresholds, we will inform\nyou to correct them. If the issues aren't resolved, Google will take down your\nintegration.\n\n### Booking Server\n\nFor all Booking Server implementations, there is a `HealthCheck` route that must\nbe included. The Actions Center periodically checks your `HealthCheck` route.\nIf it doesn't respond or returns an unhealthy response, we temporarily disable\nyour integration. We continue to periodically check your `HealthCheck` route\nand after it returns a healthy response, we automatically restore your\nintegration.\n\n|----------------------------------------------------------------------------------------------------------------------|-------|--------|\n| |||\n| `CheckAvailability` Note: This booking server endpoint is legacy. New integrations must not implement this endpoint. | \\\u003c10% | \\\u003c5s |\n| `BatchAvailabilityLookup` | \\\u003c3% | \\\u003c1.5s |\n| `CreateBooking` `UpdateBooking` | \\\u003c5% | \\\u003c4s |\n\n### RTUs\n\nFor RTUs, latency is measured by the time difference between when an action is\ntaken (for example, modifying a booking) and when Actions Center receives the\nRTU request.\n\n| **API** | **Error rate thresholds** | **Latency thresholds** |\n|---------------------------|-----------------------------------|------------------------|\n| `BookingNotification RTU` | \\\u003c10% each day and for each state | \\\u003c5 minutes |\n\nYou can monitor error rates through the various Partner Portal dashboards,\nnamely the [Feeds](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/feeds),\n[Booking Server](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/bookingserver),\nand [RTU](https://partnerdash.google.com/apps/reservewithgoogle/dashboards/realtimeupdates)\ndashboards.\n\n### Inventory Compliance requirements\n\nMake sure that you continue to follow the [Inventory Compliance requirements](/actions-center/verticals/reservations/e2e/policies/compliance-requirements).\nFor information on how a merchant can opt out of your service, see\nthe **Remove third-party links** section of\nthe [help article](https://support.google.com/business/answer/6218037?hl=en&ref_topic=11498161&sjid=1606319823142007035-NC).\nIf you violate the Inventory Compliance policy, your integration could be\ndisabled or terminated."]]