AI-generated Key Takeaways
-
The Action feed utilizes a protobuffer format but recommends JSON for feed uploads, with samples provided for reference.
-
Action feeds are structured with
ActionDetail
containing information like entity ID, link ID, URL, and actions related to an appointment. -
Legacy Action feed integrations should refer to a separate legacy feed reference for guidance.
-
Descriptor files provide information about the feed, including generation timestamp, name, and associated data files.
Create and upload action feeds
When creating and uploading action feeds, follow these instructions:
- Follow the spec described in the
action feed
for action data files. We recommend using unique action data file names for each upload.
Include a timestamp in the filename, for example,
action_1633621547.json
. - In the fileset descriptor, set the
name
field toreservewithgoogle.action.v2
. For an example of the descriptor file, refer to the JSON sample. We recommend using unique descriptor file names for each upload. Include a timestamp in the filename, for example,action_1633621547.filesetdesc.json
. The descriptor file must be uploaded to the generic SFTP server. - Upload feeds to the generic SFTP server daily as full refreshes.
- You can find SFTP server details in the Configuration > Feeds section of the Partner Portal.
- View feed ingestion status in the Feeds > History section of the Partner Portal.
Definitions
ActionFeed Definition
message ActionFeed { repeated ActionDetail data = 1; }
ActionDetail Definition
message ActionDetail { string entity_id = 2; string link_id = 3; // Deep link for action detail string url = 4; repeated Action actions = 1; }
AppointmentInfo Definition
message AppointmentInfo { }
Action Feed samples
Action Feed
{ "data": [ { "entity_id": "appointments-merchant-1", "link_id": "appointment-link-1", "url": "https://www.epapartnerwebsite.com/appointment/appointment-partner-1", "actions":[ { "appointment_info": {} } ] } ] }
Descriptor File
{ "generation_timestamp": 1677540395, "name": "reservewithgoogle.action.v2", "data_file": [ "action_1677540395_0001.json", "action_1677540395_0002.json" ] }