Knowledge · API
iGaming API versioning explained
AS Tech uses URL-path versioning (/v1, /v2) with strong backwards-compatibility guarantees. This guide explains the versioning model, breaking-change rules and migration paths.
Updated January 2025 · AS Tech iGaming editorial
URL-path versioning
Every AS Tech API endpoint carries its version in the URL path (/v1/game/launch, /v2/wallet/history). Path versioning is preferred over header versioning because it's visible in logs, easy to route and unambiguous at the edge.
Backwards-compatibility rules
Within a major version, AS Tech guarantees:
- New optional fields may be added to responses.
- New optional query params and body fields may be added to requests.
- New endpoints may be added.
- No field is ever removed.
- No field type is ever changed.
- No required parameter is ever added.
Breaking changes require a new major version
Anything that breaks the guarantees above requires bumping to v2. v1 and v2 run in parallel for a minimum 12 months. Deprecation warnings are added to v1 responses via Sunset and Deprecation headers.
Deprecation timeline
Deprecation announcement → 12-month runway → sunset. During the runway, both versions accept traffic. Operators receive Deprecation headers on every v1 response and monthly usage summaries via email.
Migration tooling
Every major-version bump ships with a migration guide, a compatibility shim (translates v1 requests to v2 for a limited period) and an automated diff tool showing every payload change on a per-endpoint basis.
Frequently asked questions
How long is a major version supported?+
Minimum 12 months after the successor version launches. Extended support is available for enterprise contracts.
Can I pin to a minor version?+
No — only major versions are pinnable. Minor versions are additive and non-breaking by design.
How do you signal deprecation?+
Sunset and Deprecation HTTP headers on every response of the deprecated version, plus email notifications and status-page banners.
Are webhooks versioned?+
Yes. Webhook payloads follow the same versioning model. You subscribe to a specific major version and can migrate at your own pace.
What's a compatibility shim?+
A translation layer that accepts v1 requests, converts them to v2 upstream and translates responses back. Runs during the deprecation window.