Salesforce API versions by release
Every Salesforce release ships a new API version: Winter '27 is API v68.0. The number appears in REST endpoints (/services/data/v68.0/), in the apiVersion of Apex classes, triggers, LWC and Aura metadata, in sfdx-project.json and in SOAP WSDLs. This table maps each version to its release and shows which versions are retired or scheduled for retirement.
Version table
| API version | Release | GA | Release number | Status |
|---|---|---|---|---|
v68.0 | Winter '27 | Oct 2026 | 264 | Current |
v67.0 | Summer '26 | Jun 2026 | 262 | Supported |
v66.0 | Spring '26 | Feb 2026 | 260 | Supported |
v65.0 | Winter '26 | Oct 2025 | 258 | Supported |
v64.0 | Summer '25 | Jun 2025 | 256 | Supported |
v63.0 | Spring '25 | Feb 2025 | 254 | Supported |
v62.0 | Winter '25 | Oct 2024 | 252 | Supported |
v61.0 | Summer '24 | Jun 2024 | 250 | Supported |
v60.0 | Spring '24 | Feb 2024 | 248 | Supported |
v59.0 | Winter '24 | Oct 2023 | 246 | Supported |
v58.0 | Summer '23 | Jun 2023 | 244 | Supported |
v57.0 | Spring '23 | Feb 2023 | 242 | Supported |
v56.0 | Winter '23 | Oct 2022 | 240 | Supported |
v55.0 | Summer '22 | Jun 2022 | 238 | Supported |
v54.0 | Spring '22 | Feb 2022 | 236 | Supported |
v53.0 | Winter '22 | Oct 2021 | 234 | Supported |
v52.0 | Summer '21 | Jun 2021 | 232 | Supported |
v51.0 | Spring '21 | Feb 2021 | 230 | Supported |
v50.0 | Winter '21 | Oct 2020 | 228 | Supported |
v49.0 | Summer '20 | Jun 2020 | 226 | Supported |
v48.0 | Spring '20 | Feb 2020 | 224 | Supported |
v47.0 | Winter '20 | Oct 2019 | 222 | Supported |
v46.0 | Summer '19 | Jun 2019 | 220 | Supported |
v45.0 | Spring '19 | Feb 2019 | 218 | Supported |
v44.0 | Winter '19 | Oct 2018 | 216 | Supported |
v43.0 | Summer '18 | Jun 2018 | 214 | Supported |
v42.0 | Spring '18 | Feb 2018 | 212 | Supported |
v41.0 | Winter '18 | Oct 2017 | 210 | Supported |
v40.0 | Summer '17 | Jun 2017 | 208 | Upcoming deprecated Summer '27, retires Summer '28 |
v39.0 | Spring '17 | Feb 2017 | 206 | Upcoming deprecated Summer '27, retires Summer '28 |
v38.0 | Winter '17 | Oct 2016 | 204 | Upcoming deprecated Summer '27, retires Summer '28 |
v37.0 | Summer '16 | Jun 2016 | 202 | Upcoming deprecated Summer '27, retires Summer '28 |
v36.0 | Spring '16 | Feb 2016 | 200 | Upcoming deprecated Summer '27, retires Summer '28 |
v35.0 | Winter '16 | Oct 2015 | 198 | Upcoming deprecated Summer '27, retires Summer '28 |
v34.0 | Summer '15 | Jun 2015 | 196 | Upcoming deprecated Summer '27, retires Summer '28 |
v33.0 | Spring '15 | Feb 2015 | 194 | Upcoming deprecated Summer '27, retires Summer '28 |
v32.0 | Winter '15 | Oct 2014 | 192 | Upcoming deprecated Summer '27, retires Summer '28 |
v31.0 | Summer '14 | Jun 2014 | 190 | Upcoming deprecated Summer '27, retires Summer '28 |
v30.0 | Spring '14 | Feb 2014 | 188 | Retired retired Summer '25 |
v29.0 | Winter '14 | Oct 2013 | 186 | Retired retired Summer '25 |
v28.0 | Summer '13 | Jun 2013 | 184 | Retired retired Summer '25 |
v27.0 | Spring '13 | Feb 2013 | 182 | Retired retired Summer '25 |
v26.0 | Winter '13 | Oct 2012 | 180 | Retired retired Summer '25 |
v25.0 | Summer '12 | Jun 2012 | 178 | Retired retired Summer '25 |
v24.0 | Spring '12 | Feb 2012 | 176 | Retired retired Summer '25 |
v23.0 | Winter '12 | Oct 2011 | 174 | Retired retired Summer '25 |
v22.0 | Summer '11 | Jun 2011 | 172 | Retired retired Summer '25 |
v21.0 | Spring '11 | Feb 2011 | 170 | Retired retired Summer '25 |
v20.0 | Winter '11 | Oct 2010 | 168 | Retired retired Summer '22 |
GA is the month the release reached the last production instances. The release number is Salesforce's internal build number (it also appears as release= in release note URLs and as the first part of the version string on Trust, for example 264.4). Rule of thumb: release number = 128 + 2 × API version.
API version retirements
Salesforce retires old API versions in blocks. After retirement, calls to those versions fail; integrations, packages and metadata pinned to a retired version must be moved to a supported one.
| Versions | Releases | Retired | Status | Source |
|---|---|---|---|---|
| v7.0 to v20.0 | Spring '06 to Winter '11 | Summer '22 (Jun 2022) | Retired | Salesforce Help |
| v21.0 to v30.0 | Spring '11 to Spring '14 | Summer '25 (Jun 2025) | Retired | Salesforce Help |
| v31.0 to v40.0 | Summer '14 to Summer '17 | Summer '28 (Jun 2028) | Upcoming | Salesforce Help |
Find the API versions your org still uses
- Apex, triggers, LWC, Aura, Visualforce: Setup > Apex Classes (and the other metadata lists) show an API Version column; sort ascending.
- Integrations: Setup > Event Monitoring or the
ApiTotalUsage/API Total Usageevent log file lists the API version each client called. - Packages: AppExchange packages carry their own version; check the package details page or ask the vendor.
- CLI:
sf project retrieve start --metadata ApexClassthengrep -h apiVersion **/*.xml | sort | uniq -c.
Which release is my org on? Use the instance lookup: type your instance (for example NA200) to see the exact release version, patch level and next upgrade weekend, straight from Salesforce Trust.
Frequently asked questions
What is the latest Salesforce API version?
API v68.0, which shipped with Winter '27. Each of the three yearly releases adds one version, so Spring '27 will be v69.0 and Summer '27 v70.0.
Which API version is Winter '27?
Winter '27 is API version 68.0. Its internal release number is 264, which is what Salesforce Trust shows as the first part of an instance's version string and what release note URLs use in the release= parameter.
How do I check which API version my org supports?
Call the versions endpoint on your My Domain: https://MyDomain.my.salesforce.com/services/data/ returns a JSON list of every supported version; the last entry is the newest. No authentication is needed for that call.
Which Salesforce API versions are retired?
Versions 7.0 through 20.0 were retired in Summer '22 and versions 21.0 through 30.0 in Summer '25. Versions 31.0 through 40.0 are deprecated from Summer '27 and retire in Summer '28. Calls to a retired version return an error, so integrations and packages pinned to them must move to a supported version.
Does the API version change how Apex or LWC behave?
Yes. The apiVersion in a class, trigger or component's metadata pins it to the behavior of that release; Salesforce keeps old versions working so existing code is not broken by a new release. Raising the version can change behavior, so test in a sandbox after updating it.
Do sandboxes and production have the same API version?
During the sandbox preview window sandboxes run the new release and expose the new API version several weeks before production. Outside that window both run the same release. Use the instance lookup to see the exact version of a given instance.
Data: /api-versions/data.json.