[null,null,["最后更新时间 (UTC)：2025-07-26。"],[[["\u003cp\u003eInventory data is transmitted to the Actions Center through feed files, which define the services, availability, and scope of the services.\u003c/p\u003e\n"],["\u003cp\u003eThe Merchants feed is mandatory for all integrations, and the Services and Availability feeds are required for end-to-end integration.\u003c/p\u003e\n"],["\u003cp\u003eAn optional Conversion feed is available to describe conversion metrics.\u003c/p\u003e\n"],["\u003cp\u003eFeeds must be uploaded with the \u003ccode\u003ePROCESS_AS_COMPLETE\u003c/code\u003e processing instruction, and \u003ccode\u003ePROCESS_AS_INCREMENTAL\u003c/code\u003e is deprecated.\u003c/p\u003e\n"],["\u003cp\u003eFeeds can be uploaded in either protocol buffer 3 (pb3) format or JSON format, with JSON recommended, and gzip compression is suggested.\u003c/p\u003e\n"]]],["Inventory data is transmitted through feed files, defining available services and their schedules. A merchants feed is mandatory for all integrations. End-to-end integrations also require services and availability feeds. An optional conversion feed tracks partnership-generated metrics. Feeds must be uploaded with `PROCESS_AS_COMPLETE`, in either pb3 or JSON format. Compressing feeds with gzip before upload is recommended. The Google Maps Booking API defines the feed structure.\n"],null,["# Feed overview (legacy)\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\nFollow the\n[legacy starter integration guide](/actions-center/legacy/archived-guides/healthcare-starter-integration-feeds)\nto 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/legacy/reference/starter-integration/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/legacy/reference/starter-integration/services-feed):** Describes the services provided by your merchants.\n- **[Availability feed](/actions-center/legacy/reference/starter-integration/availability-feed):** Lists availability slots of services provided by your merchants.\n\nSome optional feeds are also specified:\n\n- **[Conversion feed](/actions-center/legacy/reference/starter-integration/conversion-data-feed):** Describes conversion metrics that were generated by your partnership with the Actions Center.\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/healthcare/guides/tutorials/tutorial-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)."]]
