0

There are examples for using objects that are included in the SDK (eg. ET_List). How would I go about using an object that is not implemented, like AccountUser?

2

This example should help you out. If you need to use an existing user, you should do a retrieve operation rather than a create, rest of the flow remains the same.

| improve this answer | |
  • That example uses an API User for credentials. My understanding was using the SDK now you only need the Client ID and Client Secret to get a token and that's what you use for authentication. It doesn't make sense to have to have 2 authentication methods with the SDK does it? – victorcorey Aug 29 '14 at 16:04
  • Both authentication methods exist in the SDK because there are some SFMC Objects you can only use REST to interact with (e.g. Journey Builder) and vise-versa. – Adam Spriggs Jun 17 '16 at 13:41

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.