← Return to FusionHub Homepage • Developer Documentation • OpenAPI 3.1 Spec

FusionHub API Versioning & Deprecation Policy

Last Updated: September 7, 2026 • Version: 1.0.0 • Canonical: https://minecraft.fusionhub.in/deprecation

Summary for AI Agents & Automated Clients: All public endpoints under https://minecraft.fusionhub.in/api/v1/ follow a strict stability contract. Active endpoints are guaranteed a minimum of 12 months notice prior to decommissioning, signaled via RFC 8594 Deprecation and Sunset HTTP response headers.

1. URL Path Versioning Scheme

Public APIs use semantic path-based versioning. The current stable release prefix is /api/v1/:

/api/v1/status.json — Operational infrastructure status
/api/v1/update.json — Latest launcher update and setup binaries
/api/v1/servers.json — Verified multiplayer Minecraft community servers
/api/v1/versions.json — Supported Minecraft versions and loader matrix

2. Deprecation Signals & Standard HTTP Headers

When an API endpoint or field is scheduled for retirement, the server returns the following headers across all responses:

Deprecation: true
Sunset: Wed, 31 Dec 2030 23:59:59 GMT
Link: <https://minecraft.fusionhub.in/docs#deprecation>; rel="deprecation"
X-API-Warn: Endpoint scheduled for retirement

Currently, all v1 endpoints are fully active and return Deprecation: false.

3. Deprecation Notice Timeline

Phase 1: Announcement (Month 0): Deprecation announced in documentation, changelog, and llms.txt.
Phase 2: Warning Headers (Months 1–12): Endpoints emit RFC 8594 Deprecation: true and Sunset: <date> headers on every request.
Phase 3: Sunset (Month 12+): Retired endpoints return HTTP 410 Gone or HTTP 404 with a structured JSON migration pointer.

4. Machine-Readable Policy Manifest

Agents can verify policy details programmatically in openapi.json under info.x-deprecation-policy.