Laurent Maxhuni API Versioning

Laurent Maxhuni API versioning and deprecation policy.

Stable URLs and explicit lifecycle signals for agents and integrations.

This policy defines the stable API surface that agents and integrations can rely on. The public API is versioned in the URL path, and compatibility changes are announced before an endpoint is retired.

Current version

  • v1: /api/v1/posts is the canonical read-only endpoint for published posts.
  • Compatibility alias: /api/posts currently serves the same v1 contract; new integrations should use the versioned path.

Deprecation signals

When an endpoint is scheduled for retirement, responses will include Deprecation: @<unix-seconds> using the RFC 9745 structured date value, Sunset: <HTTP-date> using the RFC 8594 HTTP-date, and a Link header with rel="deprecation" pointing to this policy and migration instructions.

The endpoint remains operational during the published migration window. The replacement URL, deprecation date, sunset date, and response-shape changes will be documented here before removal. No endpoint is currently scheduled for deprecation.