Saltar al contenido principalSaltar a la navegación
Diveity Developers

[es] Changelog

[es] API version history — breaking and non-breaking changes.

# API Changelog All notable changes to the Diveity public API are documented here. Categorization rules (see [/developers/versioning](https://diveity.com/developers/versioning) for the full policy): - **Non-breaking**: adding a response field, adding an optional query parameter, fixing a bug that produced incorrect data, performance improvements. - **Breaking**: removing a response field, renaming a response field, changing a field's type, removing an optional query parameter. Breaking changes only ship in a new major version (e.g. v2). ---

2026-04-24 — v1 stable

[es] Breaking

  • None — initial release.

[es] Non-breaking

  • Initial public release of the Diveity API.
  • All `/api/v1/*` endpoints now emit the `X-API-Version` header (`X-API-Version: v1`).
  • Per-version usage tracking introduced (`public_api_key_version_usage`) — admins can now see request distribution per version per day.
  • Daily aggregation cron rolls `public_api_key_usage_logs` into the per-version summary table at midnight UTC.
  • `/developers/versioning` documents the backward-compatibility contract and the 6-month deprecation policy.

YYYY-MM-DD — short summary

[es] Breaking

  • Bullet entry... (these only ship with a new major version)

[es] Non-breaking

  • Bullet entry...