The independent daily for Salesforce admins, developers and architects

Curated by Abhinav (opens in a new tab)

Using latest for the REST API trades upgrade control for convenience (opens in a new tab)

You will learn what the latest alias for REST API versions changes, why it shifts upgrade timing onto your release testing, and why even fixed versions still depend on the current platform.

Fixed version

  • Upgrade is a planned event
  • Testing happens before the switch
  • Still runs on current platform

latest alias

  • Upgrade arrives with the release
  • No action needed to adopt it
  • Testing moves to release preview
Fixed versions and latest differ in who decides when an upgrade happens

Winter ’27 lets integrations target the REST API with the alias latest in place of an explicit version number such as v68.0. The alias removes the need to update integration versions every four months and spares you from tracking version retirements, since requests always reach the current release.

The author argues the convenience comes at a cost of control. An integration on latest picks up whatever Salesforce treats as current, so when the next version arrives, behavioral differences, new fields or updated metadata can reach your code without a planned upgrade. Salesforce recommends fixed versions for production integrations with a specific contract and latest for scripts and internal tools.

The post also points out that a fixed version does not fully protect you. Once a new version goes live, requests to older fixed versions are served by the current platform with backward compatibility applied, so the platform underneath you still changes. The author concludes that non-critical work can use latest, while critical integrations should stay on fixed versions and be regression tested every release.

Read the original at Bob Buzzard Blog (opens in a new tab)

Worth reading?