campaignmonitor/createsend-dotnet — Issue #16: createsend_dotnet.CreateSendOptions.ApiKey, multiple accounts
Author: c4ss
Created: 2011-10-18 12:51:44+00:00
State: open

I am currently trying to use two Client accounts under one application using the createsendoptions apikey property. This doesn't appear to work when switching API keys in the same request? Or even without recompiling?

I get my IEnumerable with one API and Client Key, then set the createsend_dotnet.CreateSendOptions.ApiKey to my second API key and get another IEnumerable with another Client Key.

Every time I get the 102: Invalid ClientID error on the second call for campagin details. However if I switch the order of the api keys round, the error still occurs on the second call, so the ClientID isn't incorrect as such but the library is storing my first key indefinately on compilation?