Salesforce Tooling API Queries Directly in Apex
Summary
Salesforce professionals can use Apex to query the Tooling API directly, enabling metadata queries that standard SOQL cannot handle. This approach allows automated code and metadata audits, dynamic metadata retrieval, and the creation of custom admin dashboards within LWCs. The guide details a practical Apex implementation with HTTP callouts, highlights key coding steps, and recommends best practices for production environments, like using Named Credentials and handling callout limits. This empowers teams to integrate tooling API data seamlessly inside Salesforce orgs for enhanced automation and governance.
Takeaways
- Use Apex HTTP callouts to query Tooling API endpoints internally.
- Shift to Named Credentials for secure and reliable authentication.
- Dynamically manage API versions to reduce future technical debt.
- Parse JSON responses with typed Apex classes or deserializeUntyped().
- Avoid callouts after DML to prevent System.CalloutException errors.
Step-by-Step Guide As Salesforce developers, architects, and admins, we often find ourselves needing to query metadata that standard SOQL just can’t touch. Whether you are building custom dev tools, auditing ApexClass versions, or analyzing validation rules, the Salesforce Tooling API is your best friend. While many use the Tooling API via external tools like Postman or the Developer Console, executing a /tooling/query directly within Apex unlocks powerful automation capabilities right inside your org. In this guide, we will walk through how to build and execute a Tooling API query using Apex, break down the code step-by-step, and cover essential best practices for production-ready implementations. Note: Add your Salesforce My Domain URL in Remote Site Settings. Why Use /tooling/query via Apex? Standard SOQL is built for data objects (like Accounts and Contacts). The Tooling API, however, is designed for metadata and development artifacts .