PSA: Attention API wrapper authors!
Killer Rhino.6794:
Hey gang,
Mentioned by Stefan in this recent API article:
“These new APIs, along with all previous v1 APIs, will be released under a new v2 root, which is a bit cleaner and more consistent than our v1 APIs, and offers some bulk access capabilities,” Larimore says.
Which is to say, the GW2 API will be versioned, and your wrapper’s requests and responses will need to be updated.
If your wrapper happens to be open-sourced, I’d recommend reading these pro tips on how to be a good ocommunity-developer steward, and ways to demonstrate good, positive stewardship overall.
end communication
Morhyn.8032:
I look forward to the “cleaner” API. Hopefully it will mean I can remove a lot of code from my API client.
DarkSpirit.7046:
Hey gang,
Mentioned by Stefan in this recent API article:
It is interesting that Stefan mentioned GW2Spidy when GW2Spidy is not even using the official API.
We have been asking for an official trading post API ever since Cliff started asking for API suggestions but we have not heard anything back. I hope they have an official trading post API ready for us that is mobile-friendly.
smiley.1438:
It is interesting that Stefan mentioned GW2Spidy when GW2Spidy is not even using the official API.
Where exactly does Stefan mention GW2Spidy? It’s mentioned be the articles author (who doesn’t seem to know the difference) as an example for GW2-API usage.
DarkSpirit.7046:
It is interesting that Stefan mentioned GW2Spidy when GW2Spidy is not even using the official API.
Where exactly does Stefan mention GW2Spidy? It’s mentioned be the articles author (who doesn’t seem to know the difference) as an example for GW2-API usage.
Somehow I doubt an author who, like you said, doesn’t know the difference would know so many GW2 websites that use API, on her own.