Dr. Amit Puri
0
In 2026, may your creativity scale like parameters in a neural net,
your insights converge like reasoning paths, and your actions embody the initiative of agentic intelligence.
Menu
Open
Close
Amit Puri logo Empowering Tomorrow, Today: Unleashing the Power of Citizen Development, AI Transformation, and Cloud Evolution.
Book Time @ topmate! with our experts to get help and advice, or email us on info@amitpuri.com Follow on LinkedIn

API Versioning & Deprecation Policy (amitpuri)

Official versioning lifecycle, deprecation signaling standards, and timeline guarantees for Dr. Amit Puri's REST API and agentic interfaces.

1. Semantic Versioning & Path Conventions

The amitpuri API utilizes both URL path versioning (/api/v1/*) and header-based version negotiation (API-Version: v1).

  • Current Stable Release: v1 (production active).
  • Versioned Path: https://www.amitpuri.com/api/v1/<endpoint>.json
  • Root Alias: https://www.amitpuri.com/api/<endpoint>.json points to the latest stable release (v1).
  • Response Header: Every API response contains API-Version: v1 and X-API-Version: 1.0.0.

2. Deprecation Signals & HTTP Headers

To enable autonomous AI agents and client software to detect upcoming changes without breaking in production, deprecated endpoints and versions provide standard RFC headers:

Header Standard Description & Example
Sunset RFC 8594 HTTP date when the endpoint or resource will be permanently removed (e.g. Sunset: Wed, 11 Nov 2026 00:00:00 GMT).
Deprecation RFC 9745 Date or boolean timestamp when the resource was deprecated (e.g. Deprecation: @1762819200 or Deprecation: true).
Link RFC 8288 Link header pointing to successor documentation: Link: <https://www.amitpuri.com/deprecation>; rel="deprecation".

3. Minimum Notice Timeline Guarantees

We adhere to a strict deprecation timeline so agents and developers have sufficient runway to migrate:

  • Minimum Notice Period: At least 90 days notice prior to removing or modifying any deprecated endpoint.
  • Notification Channels: Published in the OpenAPI specification (x-deprecation-policy), the Developer Portal, llms.txt, and announced via HTTP Sunset and Deprecation headers.
  • Backward Compatibility: Backward-incompatible breaking changes always increment the major version number (e.g. v2) and are served under a new URL path (/api/v2/*).

4. Machine-Readable Policy & OpenAPI Spec

Machine-readable versioning and deprecation metadata is available at:

VIEW
Close