[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eIntegrations with the Actions Center utilize Feeds, the Maps Booking API, and a Booking Server to manage and update inventory data.\u003c/p\u003e\n"],["\u003cp\u003eFeeds, in JSON or pb3 format, transmit inventory data to the Actions Center, encompassing merchant details, services offered, and availability.\u003c/p\u003e\n"],["\u003cp\u003eThe Maps Booking API enables real-time updates and booking cancellations, primarily for end-to-end integrations.\u003c/p\u003e\n"],["\u003cp\u003eA Booking Server is essential for the Actions Center to handle bookings on your behalf, utilizing a REST-based API for new integrations.\u003c/p\u003e\n"],["\u003cp\u003eStarter integrations primarily rely on Feeds for data updates and may omit the Maps Booking API and Booking Server components.\u003c/p\u003e\n"]]],["The Actions Center integration relies on three main components: Feeds, Maps Booking API, and Booking Server. Feeds, in JSON or pb3 format, transmit inventory data, including merchants, services, and availability, via SFTP upload. The Maps Booking API updates information between feed submissions and manages bookings; REST calls are used for this. The booking server is required for creating bookings. Three main feeds are mandatory: Merchants, Services, and Availability. All feeds must be uploaded in the format `PROCESS_AS_COMPLETE`.\n"],null,["This section specifies the feed files used to transmit your inventory data to\nOrdering Redirect. The contents of your feeds defines which services you are\nproviding, what services are available, and when the services are available. The\nstructure of the inventory feeds are defined by the Google Maps Booking API. The\nfollowing feeds are mandatory for the Ordering Redirect integration:\n\n- **[Merchants feed](/actions-center/verticals/ordering/redirect/reference/action-link-feeds/merchants-feed):** Contains data describing your merchants.\n\n- **[Services feed](/actions-center/verticals/ordering/redirect/reference/action-link-feeds/services-feed):** Describes the services provided by your merchants.\n\n| **Note:** All feeds must be uploaded with processing_instruction `PROCESS_AS_COMPLETE`. `PROCESS_AS_INCREMENTAL` is deprecated and cannot be used.\n\nSome fields in these feeds are required and some are optional. Any field marked\nas optional can be left out of the feed when empty.\n\nThe feeds format is described using protocol buffer 3 syntax. You have the\noption to upload the feeds file as a binary serialization of the protocol buffer\ndata in [pb3 format](/protocol-buffers/docs/proto3) or in a derived JSON format.\nWe recommend uploading the feeds in JSON format.\n\nWe recommend using [gzip to compress feeds](/actions-center/verticals/ordering/redirect/guides/tutorials/tutorial-compression)\nprior to upload.\n\nThis guide is specific to the Ordering Redirect protocol buffers. For general\ninformation on how to use the protocol buffers to generate a pb3 file,\n[here is an example in Java](/protocol-buffers/docs/javatutorial)."]]
