Call the Latest REST API Version with /services/data/latest/

Three releases a year means three version bumps in every integration. Not anymore.

Where

REST API endpoint URIs.

How

Replace the version segment, for example /services/data/v66.0/, with /services/data/latest/. The request resolves to the newest API version available in the org at call time.

Why

Integrations that only need current behavior stop accumulating stale version numbers. Pin an explicit version where you need stability; use latest where you want new fields and features to show up automatically.