Genetrix Master API Collection

Billable hours spent on setup, every project

Every Salesforce integration project begins the same way: someone spends most of a day hand-building OAuth requests in Postman, discovering which token endpoint the platform expects, and getting the variable names wrong twice before the first useful call.

It is the same day, on every project, for work that produces nothing a client would recognise as progress. This collection removes it.

Four platforms, one consistent set of variables

The collection spans SFMC REST and SOAP, Salesforce Core, Data Cloud and Agentforce — four platforms that authenticate differently and name similar things inconsistently.

The environment template normalises this. Variables are named the same way across all four, so moving between platforms mid-project does not require remembering which one calls it a subdomain and which calls it an instance URL.

Auth already solved

Authentication is where the day actually goes, and it is pre-configured here. Import the two JSON files, populate the environment with your credentials, and requests are signed and ready.

SOAP is included alongside REST, which matters more than it should: several Marketing Cloud operations still have no REST equivalent, and hand-building a SOAP envelope in Postman is unpleasant enough that people avoid the API entirely and click through the UI instead.

First public release

This is internal tooling we have used across client projects and never published. There is no blog post for it and no prior version in circulation.

The README carries a five-minute quick start and a lookup table for where to find each credential in the relevant admin UI — usually the second obstacle after auth, and the one most likely to send someone hunting through documentation.