How does the Salesforce API Retirement Surgeon prevent integration failures?

This skill proactively scans your codebase and metadata to identify legacy Salesforce API versions that are already failing (v21-30) or scheduled for retirement in Summer '27/'28 (v31-40), preventing production downtime and '410 GONE' errors.

What environments and AI agents is this skill compatible with?

The skill is designed for use with any AI agent capable of executing Python scripts or analyzing codebase structures, specifically targeting SFDX projects, Apex, LWC, and WSDL/metadata XML files.

What specific assets are included in this purchase?

You receive the scanner script, the retirement risk-tiering logic, a guided upgrade playbook, and a professional HTML/PDF report template to present exposure risks to stakeholders.

Can the skill detect API calls from external middleware or third-party integrations?

While the skill performs a comprehensive static scan of your repository, it also provides a guided walkthrough for analyzing Salesforce Event Log files to identify external calls from middleware or third-party apps that static code analysis cannot see.

Why should I use this skill instead of just asking a generic LLM to find old API versions?

Unlike generic AI prompts, this skill uses a deterministic scanner and a strict, risk-tiered playbook based on the official Salesforce retirement timeline, ensuring no nested WSDL references or package.xml versions are missed.

Does this skill address the upcoming My Domain enforcement?

Yes, beyond API versions, it identifies and flags hardcoded instance URLs (e.g., na123.salesforce.com) to help you transition to My Domain URLs before the Winter '27 enforcement deadline.

Salesforce API Retirement Surgeon SKILL.md

About this skill

Find and fix every legacy Salesforce API version before the Summer '27/'28 retirements break your integrations — scan, phased plan, CIO-ready report.

THE PROBLEM Salesforce API versions 21.0-30.0 are already retired — calls fail today with REST 410 GONE, SOAP 500 UNSUPPORTED_API_VERSION, and Bulk 400 InvalidVersion. The next wave (v31.0-v40.0) is deprecated in Summer '27 and fully retired in Summer '28. Finding every hidden version reference across code, metadata, WSDLs, and hardcoded URLs is manual, error-prone work that risks production downtime.

WHAT IT DOES

Scans your entire repository for REST, SOAP, and Bulk API version references across code and config: /services/data/vXX.X URLs, apiVersion in Apex/LWC/Aura meta.xml, package.xml, sfdx-project.json, and cached WSDLs.
Tiers every finding into RETIRED (failing now), RETIRING, AGING, and CURRENT against the official Salesforce retirement timeline.
Generates a CIO-ready HTML Retirement Exposure Report (prints to PDF) with every affected file and line number — including an "ALREADY FAILING" incident banner when retired versions are found.
Executes staged, surgical upgrades: version bumps with response-shape review, WSDL and stub regeneration, meta.xml updates gated behind the v67.0 Apex security-defaults check.
Flags hardcoded instance URLs that break at My Domain enforcement (Winter '27) — a second, independent deadline.

WHY THIS BEATS PROMPTING IT YOURSELF Generic prompting misses nested references in WSDL stubs and package.xml files and can hallucinate retirement dates. This skill uses a deterministic read-only scanner plus a strict playbook: no retired version missed, no code modified until you approve the risk-tiered plan, and dates always deferred to Salesforce's official Product & Feature Retirements list.

USE CASES

Audit a legacy codebase to find out why Salesforce integrations are throwing 410 or 400 errors.
Prepare for the Summer '27/'28 retirement wave by upgrading v31.0-v40.0 references.
Generate professional exposure reports for clients or management before starting a migration.
Convert hardcoded instance URLs to My Domain URLs before enforcement.

WORKS WITH Salesforce REST/SOAP/Bulk APIs, Apex, LWC, SFDX projects, WSDL/metadata XML. Scanner requires only Python 3.8+ (standard library).

KNOWN LIMITATIONS Static scanning covers visible code in the repo only. Callers outside it — middleware, Data Loader installs, AppExchange packages — need org-side verification via Salesforce API event logs, which the skill walks you through.

Includes: scanner script, retirement timeline & risk tiers, upgrade playbook, report spec, and a full sample Retirement Exposure Report.

Frequently Asked Questions

Salesforce api Retirement Surgeon