Services Feed Ready

The Services Feed is meant for the specific services of your merchants.

To complete the Services Feed Ready in Sandbox milestone task, you need to successfully build and upload your Services Feed to the SFTP dropboxes. The SFTP dropboxes are configured during your integration's Setup. There is a Services Feed SFTP dropbox in both Production and Sandbox environments. Ensure to use the appropriate dropbox.

Services Feed task requirements

• Minimum of one Feed upload per day for seven days.
• Include a single service for each merchant supplied in your Merchant Feed.
• Set processing_instruction to PROCESS_AS_COMPLETE.
• Fix all errors and warnings.

Note: Don't use testing data to complete milestone tasks. If you don't have a minimum of 25 merchants to build against, contact support for next steps.

Services Feed basics

Your Services Feed is an array of service definitions. Each service definition requires the following data:

• A Service ID
• The Merchant ID for the merchant associated with the service
• A localized service name

Here are the full definitions which include optional attributes that you can include to extend service behaviors.

Service ID

Service IDs don't need to be unique to each merchant, but should contain the same data across definitions. Service IDs must be unique to each merchant. As Dining Reservations End-to-End integrations only supports a single service, (unless your integration includes any Add-ons requiring additional services) we recommend using the same Service ID (for example, a service ID of "1000") to streamline Booking Server queries.

If you define a service and later change the Service ID, that means you have created two definitions in the system. A new service with the new ID, and a deleted service with the previous ID. This might cause inventory to not display if the wrong Service ID is associated with availability.

Service name

Service names must reflect the actual service. Names must not include pricing, menu items, or any other information other than the name of the service. Names must also be localized based on the user's language settings. For more information on localization, see Specify localization texts.