If you’ve ever played around with a service, plugin or app that requires an API key in order to authenticate your account, you may have noticed that it’s not the most convenient string of random characters to wield around. Great for developers, yes, but not so great if you’re on a mobile device without the liberty to copy text, or even switch between browser windows.
We realized that in order to make applications using the Campaign Monitor API more user friendly and to extend use of the API to mobile devices, it was imperative to add the new method, User.GetApiKey. This method will return the API key for a Campaign Monitor user or client, given:
- The base URL they use to login to their account
- Their account username
- Their account password
As a user’s username and password are being passed for authentication purposes, we strongly recommend that you use the HTTP Secure API endpoint for all calls to this method.
Read more on the usage of User.GetApiKey. Amazingly, there have been over 84k calls to this method since its release!
We’re very pleased to announce this method as it will inevitably overcome the usability issues that come with requesting API keys. You may even use it in your next widget! Share your questions regarding the Campaign Monitor API here and in the forums.