Support policy

How Tamr versions its SDKs and API: semantic versioning, the oldest platforms each SDK supports, how /api/v1 grows without breaking, and how to get help.

Versions

Every SDK follows semantic versioning. A minor version only adds; new parameters go last, with defaults. A deprecated message lives for at least one minor version, with its removal date in the changelog. Published versions never change: a bad release is fixed by a higher patch.

Floors

The oldest versions each SDK supports. Raising one is a major version, or ships with a maintenance branch for the old floor.

PlatformFloor
WebSafari and iOS 16.4, Chrome and Edge 111, Firefox 114, Samsung Internet 22. The script itself runs on older browsers.
FlutterFlutter 3.38.6, iOS 16, Android API 26; the Android Gradle Plugin 8.x until the webview plugin supports 9
React NativeReact Native 0.76 (Expo SDK 52), react-native-webview 13.12 to 14.x, iOS 16, Android API 26
iOSiOS 16, Xcode 16 (Swift 6)
AndroidminSdk 26, compileSdk 35, Android Gradle Plugin 8.6, Kotlin 2.1, an Android System WebView with WEB_MESSAGE_LISTENER

The API

/api/v1 only grows: new routes, new optional fields, new event types and card kinds, and new values in lists marked open in the spec, each with a fallback value such as other or unknown. Nothing is removed or narrowed in v1. A breaking change would be /api/v2, run beside v1 for at least six months. Build your client to ignore fields and events it doesn't know.

The waiter page

The page is hosted, so its fixes and features reach every app without an app release. Features that need a new SDK method say which version.

Getting help

Send the x-request-id of a failing call and the time, or the debug lines of a device session, to [email protected], or to the account manager who set the restaurant up.