[null,null,["อัปเดตล่าสุด 2025-07-26 UTC"],[],[],null,["# Availability Feed Ready\n\nThe Availability Feed provides the available slots for services of your\nmerchants.\n\nTo complete the Availability Feed Ready task, you need to successfully\n[upload](/actions-center/verticals/reservations/e2e/integration-steps/feeds#upload-feeds)\na well-formatted Availability Feed to the target environment's SFTP dropbox.\nThe SFTP dropboxes are configured during your integration's\n[Setup](/actions-center/verticals/reservations/e2e/integration-steps/setup).\nThere is an Availability SFTP dropbox for both Production and Sandbox\nenvironments. Ensure you upload to the correct dropbox by selecting the correct\nenvironment in the top menu of your Actions Center Partner Portal.\n\n### Availability Feed task requirements\n\n- Minimum of one Availability Feed upload each day for seven consecutive days.\n\n- Include 30 days of availability for each service defined in your Services\n Feed.\n\n- Set `processing_instruction` to `PROCESS_AS_COMPLETE`.\n\n- Fix all the errors and warnings.\n\n| **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](https://actionscenter.google.com/support/cases) for next steps.\n\n### Availability Feed basics\n\nYour Availability Feed is an array of availability definitions. Each\navailability definition requires the following data:\n\n- **Merchant ID**: Merchant ID of the merchant this availability slot belongs to.\n- **Service ID**: Service ID for the service that the defined availability is associated with.\n- **Start second in epoch time**: start time of the availability slot.\n\n | **Note:** Epoch time is referenced in UTC. If the venue is in a different timezone, ensure that your start seconds represent the time in UTC.\n- **Duration**: length of time that the availability is valid for in seconds.\n\n- **Resource definition** : define the slot's party size (and optionally\n define an associated room id and room name)\n [room names](/actions-center/verticals/reservations/e2e/special-features/add-dining-seating-sections)\n if appropriate for the venue.\n\n- **Spots Open**: number of available/bookable spots for the defined\n slot\n\n- **Spot Total**: Spots Total: Number of spots originally available for this\n availability slot (think of this \"spots total\" value as the denominator and the\n \"spots open\" value as the numerator in a fraction).\n\nFor more information on how to map your available inventory, see\n[Structuring availability](/actions-center/verticals/reservations/e2e/integration-steps/feeds/availability-feed/structuring-availability-data).\nThe [Availability Feed definitions and samples guide](/actions-center/verticals/reservations/e2e/integration-steps/feeds/availability-feed/samples-definitions) has optional attributes that you can\ninclude to extend service behaviors."]]
