[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eActions Center integrations are built using Feeds, the Maps Booking API, and a Booking Server to manage inventory and bookings.\u003c/p\u003e\n"],["\u003cp\u003eFeeds, in JSON or pb3 format, transmit inventory data (merchants, services, availability) to Actions Center via SFTP upload.\u003c/p\u003e\n"],["\u003cp\u003eThe Maps Booking API enables real-time updates and booking cancellations, primarily used for end-to-end integrations via REST calls.\u003c/p\u003e\n"],["\u003cp\u003eA Booking Server is necessary for Actions Center to handle bookings on your behalf, specifically for end-to-end integrations using the REST-based v3 API.\u003c/p\u003e\n"],["\u003cp\u003eStarter integrations only require the Feeds component and can disregard the Maps Booking API and Booking Server.\u003c/p\u003e\n"]]],["The core of an Actions Center integration involves three 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 handles booking cancellations using REST calls. The Booking Server, necessary for end-to-end integration, enables booking creation, utilizing the latest v3 REST API. Feeds required are Merchants, Services and Availability.\n"],null,["# Feeds overview\n\nThis section gives more details about the 3 main pieces of an integration\nwith the Actions Center. You will use each of these in the steps outlined\nin the\n[End-to-End guide](/actions-center/verticals/reservations/e2e/policies/platform-policies#merchant_and_service_eligibility).\n\nFeeds\n-----\n\n\n[Feeds](/actions-center/verticals/reservations/e2e/reference/feeds/overview)\nare files in `JSON` or\n[`pb3`](/protocol-buffers/docs/proto3) format used to\ntransmits your inventory data to the Actions Center. This allows you to\nsubmit all of your data at once to update the merchants, services, and\navailability slots using an SFTP upload.\n\nMaps Booking API\n----------------\n\n\nThe Maps Booking API allows you to update objects in the Actions Center\nsystem between feed submissions to keep information up to date. The API\nalso allows you to cancel bookings that are made through Reserve with\nGoogle\n[end-to-end integration](/actions-center/verticals/reservations/e2e/policies/platform-policies#merchant_and_service_eligibility).\n\n\nReal Time Updates are implemented using\n[REST calls](/maps-booking/reference/maps-booking-api/rest).\n| **Note:** Real Time Updates are rarely applicable for [starter integrations](/actions-center/verticals/reservations/e2e/overview). For [starter integrations](/actions-center/verticals/reservations/e2e/overview) you may ignore the Maps Booking API.\n| **Note:** Some existing legacy integration are using [RPC calls](/maps-booking/reference/maps-booking-api/rpc). This is still maintained but must not be used for new integrations.\n\nBooking Server\n--------------\n\n\nIn order for the Actions Center\n[end-to-end integration](/actions-center/verticals/reservations/e2e/policies/platform-policies#merchant_and_service_eligibility)\nto create bookings on your behalf, you\nmust set up a Booking server.\n| **Note:** This is not applicable for [starter integrations](/actions-center/verticals/reservations/e2e/overview).\n\n### REST API\n\n\nThe\n[v3 version](/actions-center/verticals/reservations/e2e/reference/booking-server-api-rest/e2e-definitions/slot-definition)\nis the latest version of the API, and supports a REST-based interface. All new integrations\nshould use the v3 API.\n\nThis section specifies the feed files used to transmit your\ninventory data to the Actions Center. The contents of your feeds defines\nwhich services you are providing, what services are available, and when the\nservices are available.\n\n\nCheck the **References and Samples** accordion to learn how to share these feeds with us.\n\nThe structure of the inventory feeds are defined by the Google Maps Booking\nAPI.\n\nThe following feed is mandatory across any integration:\n\n- **[Merchants feed](/actions-center/verticals/reservations/e2e/reference/feeds/merchants-feed):** Contains data describing your merchants.\n\nIn addition, the 2 following feeds are mandatory for end-to-end integration.\n\n- **[Services feed](/actions-center/verticals/reservations/e2e/reference/feeds/services-feed):** Describes the services provided by your merchants.\n- **[Availability feed](/actions-center/verticals/reservations/e2e/reference/feeds/availability-feed):** Lists availability slots of 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\nmarked as 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\nbuffer data 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\n[gzip to compress feeds](/actions-center/verticals/reservations/e2e/reference/tutorials/compression) prior to upload.\n\nThis guide is specific to the Actions Center protocol buffers. For\ngeneral information on how to use the protocol buffers to generate a pb3\nfile,\n[here is an example in Java](/protocol-buffers/docs/javatutorial)."]]
