{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
впервые опубликовано в:BungieNetPlatform
Смотреть всю тему
Изменено (Eriena):
6/8/2017 3:44:33 AM
1
Help getting started
Hi,
I'm new around here and wanted to say hello, as well as try to get some guidance on using that wonderful API of yours ,as there are some ideas I'd like to try out.
I just done reading a few posts like
[url=https://www.bungie.net/en-US/Clan/Post/39966/85087279/0/0]API Intro
[/url], [url=https://www.bungie.net/en/Help/Article/45481]Bungie.net Authentication[/url] and
[url=https://www.bungie.net/en/Clan/Post/39966/227773391/0/0]OAuth 2.0 details[/url]
I bookmarked [url=https://www.bungie.net/platform/destiny/help/]Destiny[/url],[url=https://www.bungie.net/platform/user/help/]User[/url] and [url=https://www.bungie.net/platform/forum/help/]Forum[/url] documentation, as well as [url=http://destinydevs.github.io/BungieNetPlatform/]the Wiki[/url], [url=https://github.com/DestinyDevs/BungieNetPlatform]gitHub[/url] and [url=https://www.bungie.net/en/Clan/Post/39966/208998725/0/0]the resources post[/url]
I "main" [b]C#,[/b] but also know how to use Javascript and PHP with no problem.
Any suggestions what to check next?
Oh, and if possible, could you help me out with a few questions?:
What is it the "Not Applicable" client type?
Why would the client send the Redirect URL optional parameter?
Can the "Redirect URL" be changed later ?
Finally... (if possible) What setting should be used to run an authenticated client side app?
(like pure HTML/JS App without server. Should the api key be created using Client Type:"Public" and Redirect URL empty)
Excuse my poor english and thanks!
-
Изменено (Tetron): 6/10/2017 3:00:43 PMWhat is the "not applicable" client type? This means you are not using oauth. You either are not authenticating at all, and just need an API key so you can call the non-authenticated APIs (of which there are many). You would also use this if you are using our original authentication implementation (but don't do that). In the case of our current OAuth support, clients would never need to send the redirect URL parameter. But, if you are using a pre-made OAuth SDK, it may send it anyway which is fine as long as it matches what you have configured in the portal. Yes, the redirect URL can be changed at any time. Typically, you will go through several iterations while you are developing. A pure HTML/JS app that runs in a user's browser should use the 'public' client type since there is no way to keep a secret. Your English is fine! Have fun with this!
