0

Anything counts as long as the tooling API was critical to the functionality of the project. This includes Andrew Fawcett's Apex wrapper around the API.

https://github.com/afawcett/apex-toolingapi

  • 1
    In order to make this question useful, we'll have to put up a community wiki, but I'm not sure what the point of the question is? – sfdcfox Apr 3 '17 at 18:38
  • Yeah I got an alert while asking the question that stackexchange prefers questions that can be definitively answered. I'm more looking to discuss... where should I post this? – Sam Kamensky Apr 3 '17 at 18:41
  • 1
    I'm not saying that such a question "can't" exist here (for example, we have a Q&A for force.com IDEs), but for an actual discussion, consider the DeveloperForce forums or the Salesforce Community, which are amenable to such discussions. – sfdcfox Apr 3 '17 at 18:44
  • 1
    I agree this question is off topic here but am somewhat leery to unilaterally close it... – Adrian Larson Apr 4 '17 at 2:15
  • @AdrianLarson, I know THIS is off topic, but that was a beautiful sentence. – Sam Kamensky Apr 4 '17 at 15:46
2

Just about any tool that is built for Salesforce developers will touch the Tooling API for some or all of its functionality. The Metadata API alone can't perform all the operations that the Tooling API can. More common would be to use a combination of these two APIs and then some (Streaming API, Partner/REST API, Bulk API)

Here is an extract from Tools for Development that I know for sure use the Tooling API:

Even the Developer Console uses the Tooling API for a majority of its calls. It is also used with the Salesforce DX command line.

  • Thanks! This is a wonderful list that will lead to some nice reading. – Sam Kamensky Apr 4 '17 at 15:45

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.