Ringkasan feed
Tetap teratur dengan koleksi
Simpan dan kategorikan konten berdasarkan preferensi Anda.
Bagian ini menentukan file feed yang digunakan untuk mengirimkan data inventaris Anda ke Actions Center. Konten feed Anda menentukan layanan mana saja yang Anda berikan dan layanan apa saja yang tersedia.
Struktur feed inventaris ditentukan oleh Google Maps Booking API.
Feed berikut wajib ada untuk integrasi Pengalihan Janji Temu:
- Feed entitas: Berisi data yang mendeskripsikan entitas Anda.
- Feed tindakan: Berisi data yang mendeskripsikan deep link yang terkait dengan entitas Anda.
- Feed layanan: Mendeskripsikan layanan yang disediakan oleh
entitas Anda.
Beberapa kolom dalam feed ini wajib diisi dan beberapa lainnya bersifat opsional. Kolom apa pun yang ditandai sebagai opsional dapat dihapus dari feed jika kosong.
Format feed dideskripsikan menggunakan sintaksis protocol buffer 3. Anda memiliki
opsi untuk mengupload file feed sebagai serialisasi biner data
buffer protokol dalam format pb3 atau dalam format JSON turunan.
Sebaiknya upload feed dalam format JSON.
Sebaiknya gunakan
gzip untuk mengompresi feed sebelum mengupload.
Panduan ini ditujukan khusus untuk buffer protokol Actions Center. Untuk
informasi umum tentang cara menggunakan protocol buffer guna menghasilkan file
pb3,
berikut adalah contoh di Java.
Kecuali dinyatakan lain, konten di halaman ini dilisensikan berdasarkan Lisensi Creative Commons Attribution 4.0, sedangkan contoh kode dilisensikan berdasarkan Lisensi Apache 2.0. Untuk mengetahui informasi selengkapnya, lihat Kebijakan Situs Google Developers. Java adalah merek dagang terdaftar dari Oracle dan/atau afiliasinya.
Terakhir diperbarui pada 2025-07-26 UTC.
[null,null,["Terakhir diperbarui pada 2025-07-26 UTC."],[[["\u003cp\u003eInventory data is transmitted to Actions Center using Entity, Action, and Services feeds, defining your provided and available services.\u003c/p\u003e\n"],["\u003cp\u003eFeed structures are based on the Google Maps Booking API, with mandatory feeds for Appointments Redirect integration including Entity, Action, and Services.\u003c/p\u003e\n"],["\u003cp\u003eFeeds can be provided in pb3 or JSON format (JSON recommended), with optional fields allowed to be omitted when empty.\u003c/p\u003e\n"],["\u003cp\u003eGoogle recommends compressing feeds using gzip before uploading them to Actions Center.\u003c/p\u003e\n"]]],["Inventory data is sent to the Actions Center via feed files, which define offered services and their availability. Mandatory feeds for Appointments Redirect integration include: Entity, Action, and Services feeds. These files can be uploaded in either protocol buffer (pb3) or JSON format, with JSON recommended. Optional fields can be omitted. Feeds are structured according to the Google Maps Booking API, and compressing the feeds using gzip prior to upload is recommended.\n"],null,["This 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 and what services are available.\n\nThe structure of the inventory feeds are defined by the Google Maps Booking\nAPI.\n\nThe following feeds are mandatory for the Appointments Redirect integration:\n\n- **[Entity feed](/actions-center/verticals/appointments/redirect/reference/feeds/entity-feed):** Contains data describing your entities.\n\n\u003c!-- --\u003e\n\n- **[Action feed](/actions-center/verticals/appointments/redirect/reference/feeds/action-feed):** Contains data describing your deep links associated with your entities.\n\n\u003c!-- --\u003e\n\n- **[Services feed](/actions-center/verticals/appointments/redirect/reference/feeds/services-feed):** Describes the services provided by your entities.\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/appointments/redirect/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)."]]
