API Migration

[jsassner]

From the new https://dev.battle.net/ site release today:
"The existing Battle.net Community APIs are being migrated to a new host. The WoW, SC2, and D3 APIs hosted at *.battle.net/api are being moved to *.api.battle.net. We're also changing the protocol from HTTP to HTTPS."

Also an API key have to be added as an parameter to the library:
"When communicating with the community APIs using Mashery, you'll need to provide your API key in the query parameters of all requests as the "apikey" parameter."

Is this project still active? I'm using this as part of http://www.guildtoolkit.com (which is in RC state)

[Grepster]

We saw a merge request recently so there is at least one person still hacking on it. Briandek is reviewing that one. I will try and read up on the change and push out an update for that in the next week or two.

[briandek]

I'll spend some time this weekend updating the API. I've been out of the loop on the api migration, so thanks for the heads up. I should have something stable by next week.

[jsassner]

Thank you. Let me know if you want help testing.

[briandek]

updated* - you should be able to pick it up from nuget package manager in VS.

The library has been updated to require the Mashery API key since that seems to be the direction the API is headed into, so in order to instantiate a WowExplorer you'll have to give it an API key provided when you create a mashery account.