Api: Can't seem to access getDestinyProfile. It keeps giving me an error. I'm super new to this and am practicing api calls with my favorite game.

Created on 14 Aug 2018  路  3Comments  路  Source: Bungie-net/api

I've been able to access a lot of cool information so far, but am having trouble with getting my profile data. I'm wanting to get my specific characterIDs so I can look up stats based on their ID. I can't seem to find my ID so I figured If I accessed my Destiny Profile it would list it.

Maybe It's me who's missing something (Most likely the case). Any Help/Advice would be great!

The call I'm trying to make is...GET: /Destiny2/{membershipType}/Profile/{destinyMembershipId}/

errors

enhancement

Most helpful comment

Sweet, no problem! Glad to be of help! (and sorry about the shitty error message! "InvalidParameters...? which ones?" Yuck!)

All 3 comments

Ah, so the trick of this is that it requires a ?components= querystring parameter. Unfortunately, the error message we return sucks badly. I didn't actually realize until you posted that screenshot just how useless our error message is for this scenario!

The components querystring parameter allows you to customize how much data you get back (if you ask for everything, it can be more than 1mb! So avoid asking for components you don't need if you want to save bandwidth costs and increase your app's responsiveness!). It's a comma separated list of values. The possible values are as follows, you can use either the name or the numerical value:

https://bungie-net.github.io/multi/schema_Destiny-DestinyComponentType.html#schema_Destiny-DestinyComponentType

So for example, if you just want characters' summary data you can call:

/Destiny2/{membershipType}/Profile/{destinyMembershipId}/?components=Characters

But if you want their progress (which has things like their Milestone data) you can call:

/Destiny2/{membershipType}/Profile/{destinyMembershipId}/?components=Characters,CharacterProgressions

... I need to also make the error message better. I'm going to log a bug on that.

Thanks for the quick response my guy! Great answer, completely helped me out! I appreciate it!

Sweet, no problem! Glad to be of help! (and sorry about the shitty error message! "InvalidParameters...? which ones?" Yuck!)

Was this page helpful?
0 / 5 - 0 ratings