> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Field Migration Guide Jan 2026

## Article: Field Migration Guide Jan 2026

## Article Link: https://dev.wix.com/docs/api-reference/business-solutions/restaurants/reservations/field-migration-guide-jan-2026.md

## Article Content:

# Reservations APIs Field Migration Guide

This guide helps you update your code to use improved fields in the Reservations APIs. We've made several fields easier to use and more consistent across the APIs.

**What's changing:** We're deprecating some fields and introducing cleaner alternatives. This guide provides a quick reference for updating your code. Make sure to update your code by February 28, 2026, when these fields will no longer be supported.

## What's improved

1. **Simpler Conflict Handling**: Instead of three separate flags (`force`, `ignoreTableCombinationConflicts`, `ignoreReservationLocationConflicts`), just use one: `ignoreConflicts`.

2. **Clearer Field Names**: We've updated some names for consistency:
   - `partiesSize` → `partySize`
   - `tableIds` → `tables.ids`

3. **More Approval Options**: `manualApproval` is now `approval` to support additional approval types beyond manual.

4. **Automatic Field Access**: No more `fieldSet` or `fieldsets` parameters in Reservation Location requests. The API now automatically returns all fields you're authorized to access.

5. **Cleaned Up Statuses**: Removed unused `PAYMENT_PENDING` status from reservations.

6. **Unified Availability Checks**: Time slot responses now use one field (`timeSlotAvailability`) instead of separate fields for different conflict types.

## Field reference

### Reservation Location object

| Old Field Name                                            | New Field Name                               | Notes                                                                                      |
| --------------------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------ |
| configuration.onlineReservations.partiesSize              | configuration.onlineReservations.partySize   | Renamed to singular form for consistency                                                   |
| configuration.onlineReservations.manualApproval           | configuration.onlineReservations.approval    | Renamed to support more approval types beyond manual                                       |
| configuration.myReservationsFields                        | -                                            | **Removed completely**. This field is no longer supported                                  |

### Reservation Locations methods

All `fieldSet` and `fieldsets` parameters have been removed from the following methods:
- GetReservationLocation
- QueryReservationLocations
- ListReservationLocations

These methods now automatically return all fields you're authorized to access. When sent, they are ignored.

### Reservation object

| Old Field Name                                  | New Field Name                    | Notes                                                                                      |
| ----------------------------------------------- | --------------------------------- | ------------------------------------------------------------------------------------------ |
| details.tableIds                                | details.tables.ids                | Restructured into nested object for better organization                                    |
| Status.PAYMENT_PENDING                          | -                                 | **Removed**. This status is no longer used in the reservation workflow                     |

### Reservations methods

Multiple conflict-handling flags have been consolidated into a single `ignoreConflicts` parameter for both Create and Update operations.

| Old Field Name                                            | New Field Name                               | Notes                                                                                      |
| --------------------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------ |
| CreateReservationRequest.force                            | CreateReservationRequest.ignoreConflicts     | Consolidated flag for all conflict scenarios                                               |
| CreateReservationRequest.ignoreTableCombinationConflicts  | CreateReservationRequest.ignoreConflicts     | Consolidated flag for all conflict scenarios                                               |
| CreateReservationRequest.ignoreReservationLocationConflicts | CreateReservationRequest.ignoreConflicts   | Consolidated flag for all conflict scenarios                                               |
| UpdateReservationRequest.force                            | UpdateReservationRequest.ignoreConflicts     | Consolidated flag for all conflict scenarios                                               |
| UpdateReservationRequest.ignoreTableCombinationConflicts  | UpdateReservationRequest.ignoreConflicts     | Consolidated flag for all conflict scenarios                                               |
| UpdateReservationRequest.ignoreReservationLocationConflicts | UpdateReservationRequest.ignoreConflicts   | Consolidated flag for all conflict scenarios                                               |
| GetReservationRequest.fieldSet                            | GetReservationRequest.fieldsets              | Standardized to plural form for consistency                                                |

### Time Slots methods

Time slot availability information has been consolidated into a unified response structure.

| Old Field Name                                  | New Field Name                               | Notes                                                                                      |
| ----------------------------------------------- | -------------------------------------------- | ------------------------------------------------------------------------------------------ |
| CheckTimeSlotResponse.tableCombinationAvailability | CheckTimeSlotResponse.timeSlotAvailability | Unified availability response                                                              |
| CheckTimeSlotResponse.reservationLocationConflict  | CheckTimeSlotResponse.timeSlotAvailability | Unified availability response                                                              |

---

**Last Updated**: Jan 2026