generated: '2026-06-20'
method: searched
source: developer.salesforce.com API version + release documentation
notes: >-
  Salesforce versions its platform APIs with a monotonically increasing integer version in the
  URI path (vNN.0), incremented once per seasonal platform release (Winter/Spring/Summer). Older
  API versions are supported for a long window; Salesforce has announced retirement of legacy
  versions (v7.0-v20.0 and v21.0-v30.0 in past cycles), so very old versions eventually return
  errors. There is no per-endpoint Sunset/Deprecation header contract on data APIs; deprecation
  is communicated via Release Notes and the API version-retirement notices.
versioning:
  scheme: uri-path
  format: v{NN}.0
  current: v67.0
  current_release: Summer '26
  cadence: 3 seasonal releases per year (Winter, Spring, Summer)
  docs: https://developer.salesforce.com/docs/atlas.en-us.api_rest.meta/api_rest/dome_versions.htm
  discovery: GET https://{instance}.salesforce.com/services/data/ (unauthenticated version list)
  recent_versions:
    - {version: v67.0, release: Summer '26}
    - {version: v66.0, release: Spring '26}
    - {version: v65.0, release: Winter '26}
    - {version: v64.0, release: Summer '25}
    - {version: v63.0, release: Spring '25}
    - {version: v62.0, release: Winter '25}
deprecation:
  policy_url: https://help.salesforce.com/s/articleView?id=000392347&type=1
  mechanism: Release Notes + API version retirement announcements
  sunset_header: false
  legacy_retired: API versions 1.0-30.0 retired in prior cycles.
sla:
  url: https://www.salesforce.com/company/legal/sla/
  note: Contractual uptime commitments are per-customer/edition; Salesforce publishes trust status rather than a single public SLA percentage.
status_page: https://status.salesforce.com/
release_notes: https://help.salesforce.com/s/articleView?id=release-notes.salesforce_release_notes.htm