I have been trying to figure out something similar for about a day. In my case I want to integrate newsletter subscriptions (newsletters from me) for users of my application where they can manage subscriptions (multiple mailing lists) from my app settings, my app would then take their preferences and manage that on my CTCT account via the API. The problem is that there is no room for OAuth for the users, it doesn't make any sense either. With v3 it is obvious that v2 allowed for two use cases. In v2 you could generate access token and leave that in the system settings and have access to the one account you wanted to manage. This probably wasn't how the API was intended to use, but this hack worked. The second use case, which is the only one that v3 allows, is that you use an app through which you can interact with you CTCT account. This is perfect for most scenarios where there is a personal interaction, like setting up a plugin for Wordpress. This is lacking for automated systems like mines where I need to setup some initial button in administration to click to trigger the OAuth flow to get the needed credential (not to mention building the entire OAuth flow and management just for this) instead of simply calling the API with my username & password for authentication. That is my take on this. Please correct me if I'm wrong and/or missed something.
... View more
