5

As per this documentation you should use a single credential set: AppExchange Partners: Use the Same Client ID and Client Secret Multi-tenant AppExchange apps use the same client ID and client secret for all of their customers. Marketing Cloud automatically enables this as part of the AppExchange app publishing and installation process. More ...


5

This is a feature of OAuth, and is working as designed. A connected app clientId and secret can be used to connect to any org provided you go through oauth flow and enter username and password (or alternatively provide them using the username-password flow). Note that you will still need username and password for the PROD and cannot access anything allowed ...


4

If you log into the relevant Business Unit, Click Administration from the drop down under your user name. Then Account > Installed Packages You should see a list of installed packages, select the relevant package, you should then see the clientID and Secret.


4

These depend on what stack you are on. you can check what stack your are on by: Going to trust.marketingcloud.com and entering your MID number log into marketing cloud and check the prefix to the url. It would be ssomething eg s7.mc.exacttarget.com would mean you are on the s7 stack Endpoint Links Stack WSDL Link S1 Instance https:...


2

Once you have created a connected app at the bottom of the "Apps" page, do not click on "Edit" or "Manage" but instead click on the connected app name which is a hyperlink. That "Connected App Name" page will show the "Consumer Key" and the "Consumer Secret" (once you click on "Click to reveal" link).


1

Client Credentials grant type is not supported by Salesforce. Recommended (and better) alternative for app-to-app calls is JWT Bearer.


1

Please look at the answer here: Query a data view of a child business unit from the parent According to SFMC Support, you cannot query a Child BU from the Parent, but you can query the Parent from the Child.


1

@AMM, it looks like all you need to do is set the client element within the CallOptions header when making API calls. Take a look at the screenshot below showing a report that lists the custom Client ID sent with an API call. Below is the snippet of Ruby code I used to produce that audit record. login_header = { "tns:CallOptions" => { "tns:client" => ...


Only top voted, non community-wiki answers of a minimum length are eligible