I think I know the answer to this question already, but I need to ask it nonetheless.
Our system is making a request to https://api.constantcontact.com/v2/account/info to get back information about the account. However, there is no unique identifier for that account (i.e., GUID, integer value, etc.). This is very problematic for us because our users may be accessing the same CC account, or may be authenticated into their own CC account. We apparently can't do account-level processing or rollups because our system doesn't know which CC account each user belongs to.
So I suppose the question is, do you have any workaround for us, or do you have this api feature enhancment (give account identifier in the JSON response) on your development backlog?
Solved! Go to Solution.
While it's not possible to get a unique account ID, it is possible to get the username that was used to create your access token at any time by calling this endpoint:
You can also store the username associated with an Access Token when it is provided along with the token at the end of the OAuth flow. However, if you're looking to do special processing when there are actions from multiple unique users in the same Constant Contact account, there's not currently a method available to get an identifier for the account other than the username. I also checked to be sure and there is not currently a plan to expose a separate identifier from the username for identifying an account.
Would it be possible for you to decribe the use-case for how you would use an account ID rather than a username?
Your feedback is appreciated, but please help me understand the following:
1) I don't see any way (through the api) to get a list of usernames for an account. Can you confirm whether this is possible or not?
2) Are IDs (such as contact Id, campaign Id, contact list Id, etc.) unique across the entire Constant Contact system? Or only guaranteed to be unique within the account?
Here's some info for your questions:
If there is any additional info that I can provide, please let me know!
Not exactly what I wanted to hear, but thanks nonetheless. Regarding your point about "Contacts/lists that were created before the transition" -- can you tell me when (year or month/year) this "transition" occurred? Just trying to understand how far back this goes and whether we will have any problems with our existing clients or future clients.
Regarding the transition, it's not possible to give an explicit date because it was a rolling transition that happened over the course of many months. However, the majority of users (>90%) would have all been transitioned by July 2014. It is important to note that even for accounts that were transitioned to the new system, all new data created after the transition will have unique identifiers.
In terms if using items such as contacts or lists as a way to identify a given account, you could do the same by creating a new List with a specific name if it does not already exist. Since the list is new, it would be guaranteed to have a unique ID.
Let me know if you have any questions!