A Salesforce API Collection

I have found myself back in SaleForce doing some work, and rather than code wrangling to get the access I needed I created a SalesForce Postman collection and environment, allowing me to quickly get at the MANY objects and records available to me within the SaleSforce ecosystem. While the Postman collection doesn’t reflect 100% of the surface area of the SaleForce REST API, with over 800 individual requests it covers a significant portion of what is available via the CRM API.

The SalesForce REST API has an endpoint where you can query for a list of objects, an then pass those objects in as a path parameter. This approach to designing APIs, or what I’d consider to be a lack of API design was a common pattern from 2000 through 2010, and is something you still see fairly often from providers in 2019. To help simplify things for potential consumers I when ahead and crafted a path for each of the SalesForce object, essentially doing the API design work for them. You can see the APIs via documentation I published from the Postman collection.

I included a Postman environment with the documentation and supporting Postman collection, providing the base URL and version for the API. Depending on what version you decide to use, the list of available objects will vary. There are also some API paths I do not include dealing with the GUI, widgets, etc. I was looking to publish a usable collection that would allow me to get at the core data available within SaleForce. As part of a separate wave of work I will add in the ability to add, update, and delete objects, expanding the reach of the collection, allowing users to read and write data, instead of just pulling data.

Hopefully you find the SalesForce collection helpful. If there are missing paths you’d like to see in there, or would like to get help setting up the OAuth, let me know. I found their instructions for setting up an application overly complicated, but such is the case when it comes to OAuth. I’m always surprised how much friction can be injected into the process, so if you get confused don’t worry about it—I have setup over a hundred OAuth flows, and this one was pretty difficult. I will keep investing in the SalesForce collection, and keep autogenerating it from the dynamic list of objects, helping me keep it up to date with each version, hopefully keeping it in sync with the latest coming out of the platform.