Hi,   I am working on an integration with Constant Contacts API on a multi-tenant system held on multiple app servers. Basically, we let them integrate their "members" on their tenants to their Constant Contact account, and depending on some conditions those members get synced to their constant contact account. We integrate their account by using V3 OAuth, storing the access token and refresh token, and using that access token to query/post to the API. So Every tenant will have their own access token going to their own account.   This all has been working but I have run into a problem with rate throttling because we run on multiple app servers we then have the chance of running the sync to constant contact at the same time on different app servers. I never would have thought this was an issue but I noticed whenever both servers were running the sync at the same time it was giving me a rate throttle error of "Too Many Requests". From my understanding, this error occurs when you make over 4 requests per second.   Now my confusion and question here are, I would think the throttle would be on the access token and not the API key that generated the access token. I'm having trouble seeing any documentation saying if the throttle is on the api key that generated the token or if they are separate so this is leading me to believe that the throttle is based on the api key that generated the access token. If this is true, is this intended? The reason I ask is we integrate on other systems using the same method and we always see the throttle on the access token, never the api key generating the access token. This way you don't end up getting throttled just because you end up with a lot of customers. At the moment I am planning on creating a single app service that will handle all the servers so only one sync will run at a time but want to avoid that if possible.   Am I correct in my assumption or am I possibly getting the throttle for other reasons?   Thanks! ... View more