Live Versions

Endpoints	Changes
https://recognition.services.tiliter.com/ https://recognition.services.tiliter.com/v1/14/	Initial version
https://recognition.services.tiliter.com/v1/15/	Added ability to detect paper bags

See https://developer.tiliter.com/changelog for changes between versions

Why Versioning Matters

Our enterprise customers rely on Tiliter’s Recognition API in production systems where any unexpected change can cause significant disruption. Even small updates that seem harmless can result in downtime for customers, which often takes months for internal teams to resolve.

To prevent this, Tiliter maintains multiple live versions of the Recognition API in parallel. Each version is a separate instance of the service with its own behavior. This means existing integrations remain stable, while new features can be introduced in newer versions without disrupting current customers.”

How Versioning Works

Version Numbers

We use the format A.B.C:

A = Open API breaking change
B = Tiliter customer breaking change
C = Minor refactor, bugfix, or model update

Version in the URL

Versions are specified directly in the API URL:

https://recognition.services.tiliter.com/v1/14/ → Version 1.14.x
https://recognition.services.tiliter.com/v1/15/ → Version 1.15.x

Here, A (1) and B (14, 15) are part of the URL.

C (the patch version) is not in the URL - you’ll always get the latest stable patch within that minor version.

Default Endpoint

The unversioned /recognition endpoint is permanently mapped to v1.14.x.

It exists only to support legacy customers who integrated before versioning was introduced.
It will not move forward to newer versions.
All new integrations must use versioned URLs (e.g. /v1/14/recognition/, /v1/15/recognition/).

Lifecycle & Deprecation

Versions remain live as long as customers are actively using them.
If no customers are on a version, we may deprecate it.
If only a small number of customers remain, we will coordinate with them to plan a migration to a newer version.

Benefits for You

✅ Zero Unexpected Breakage - Your integration will not change unless you choose to upgrade.
✅ Parallel Support - Multiple versions run side-by-side, so you can upgrade when it suits your business.
✅ Future-Proofing –-You get the stability of today’s integration and the flexibility to adopt tomorrow’s features.

👉 In short: Tiliter’s API versioning ensures you can move at your own pace - keeping your systems reliable, while still unlocking new capabilities when you’re ready.