Hi HandySolo, I think the site’s instructions are not quite comprehensive enough. And your comment didn’t clarify anything for me personally – here’s why:
I installed the software on my own hosting account, and in the process I made a WordPress support login.
I know that WordPress.COM is “not my blog”. I also know that I don’t have a WordPress.com “account” because (as I see it, maybe wrongly) I don’t *want* a blog on WordPress; it seems odd that i would need to create an account i don’t plan to use in order to get an API Key for use on my site.
But the instructions at: https://wordpress.com/api-keys/
do say I can “leverage the power of WP.com while still hosting your blog elsewhere” — so perhaps I must have an account after all. But wait… why would that be? I’m not hosting on WordPress.COM… and will I need a new account for every blog i install elsewhere?? Hmm, unclear.
So logically I then think maybe I can get an API Key for MY blog via my Support identity, which is more universal. But no; there’s no mention of the API Key in my profile.
Which leads me to this forum to see what other users did *before* I create an unwanted .COM account.
See the issue? Where is it explained that a Support account is insufficient to get an API Key, or what to do about one API Key handling several installations?
This said, i’m creating an account now ??
…
Okay, I’m back – i see now that wordpress.com offers an option to just create a *username* (not a blog) for seemingly just this purpose of getting the API Key. Nice…. everything was thought of.
Now the instructions could be updated a tiny bit!
Hope this post helps someone.