New policy for API enum fields

Starting July 20, 2026, the addition of new values to an existing enum will no longer be treated as a breaking change. The list of possible values for these enums is now considered "open." This open enum policy provides your team with new Toast functionality immediately.

• No 90-day lead time: Toast APIs may add new values to enums (such as new order states, dining options, or card types) at any time. We will announce these new values via release notes as they are deployed, but without a 90-day notice period.

• Continued notice of breaking changes: The Toast technical communication team will still provide a 90-day notice for breaking changes, such as removing an existing enum value or renaming a field.

To ensure your integration remains stable when new values are introduced, verify that your code handles unrecognized enum values:

• Use default cases: Ensure all switch, match, or if/else statements include a safe default case to prevent application crashes.

• Handle unrecognized values: Design your integration to ignore or generically display unrecognized values until you choose to update your local client libraries.