{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
originally posted in:BungieNetPlatform
2/4/2015 12:27:56 PM
8
About the COR,
what's the status of supporting javascript Request with an API key.
I would like that feauture to be availble in the future.
English
-
So when exactly would cor come to play? Im thinking possibly if we authenticate using a service then allow user to update their own bungie.net account. Is this correct? Digressing: I'm building my own api for a different application. I was scratching my head as to how to auth my own key, and I find the x-api-key header a novel alternative. Is that standard? I believe anything with a X- prepend is custom; right? Personally I was looking at a key/datetime/passcode with md5 type coding passed in the request. Is the header approach better?
-
COR might probably never come out and play due the lack of interest, i was the first one who was interested. The header aproache is better for the authentication, you cannot modify the headers with a GET request. When you have the Cookies of a Signed In user and the API key of course, you can do the same stuff as you can do by hand. Send me a PM if you need some help
-
Ive used cor for other apps (might need tp actually add it for my latest), i was just wondering the use case for the bungie api. Not sure bungie wants ability to change add from external source, which is what i would guess cor would be needed. Looks like this api is read only.
-
Thanks for letting us know. Can you give me some idea of the scenario you would like to implement? You can PM me if you prefer.
-
I was going to write a small app to do some targeted statistic reporting but that morphed into first writing an Angular service which to be easily implemented by others needs to have access to the API from the browser.
-
Hi, I'm also interested in Javascript access to the API. My biggest concern is that I'm creating a simple Pebble Watch app that pulls in guardian statistics, and since I don't have the resources for a dedicated proxy host to the API, I have no means of querying for a user's info due to the Cross-Origin restrictions. An example would be that I host a simple page on GitHub: http://phatsk.github.io/destiny_pebble/ The page will eventually get some style, if it ends up being usable, but currently I can't make the call to grab the user's profile info. This seriously hobbles my app, as I can only show certain information from things like the Advisors endpoint in the app. N.B. This would all be moot if I had a dedicated server that I could proxy the request through, but that's not currently feasible for me. I also think that there are a lot of developers out there who would get a great use out of being able to access the API via Ajax/CORS/JSONP whathaveyou. Thanks!
-
I am not sure about the software architecture for Pebble, but it is the web browsers that enforce an origin policy. If you are not running javascript in a browser, you should not need any type of CORS support.
-
I'll take a look - my guess, since I'm using their JS framework, is that a browser is at some level "emulated" to give events and such. Regardless, it does make debugging quite a pain ;) I found a free service to do my hosting for now, but I could see this being advantageous for developers regardless, especially when it comes to quickly prototyping functionality.
