So while [url=http://bungienetplatform.wikia.com/wiki/GetAdvisorsForCharacter]GetAdvisorsForCharacter[/url] has its privacy inspected, the [url=http://bungienetplatform.wikia.com/wiki/GetAdvisorsForCurrentCharacter]private endpoint[/url] now returns the "Checklists" advisor. Here's what it looks like: [spoiler]"checklists": [ { "identifier": "CHECKLIST_CALCIFIED_FRAGMENTS", "checklistName": "[Calcified Fragments]", "checklistDescription": "[... they're sticky. They taste like pie and\/or victory.]", "cards": { "700680": true, "700690": true, "700780": true, "700790": true, "700810": true, "700820": true, "700830": true, "700840": true, "700850": true, "700860": true, "700870": true, "700880": true, "700700": true, "700890": true, "700900": true, "700910": true, "700920": true, "700930": true, "700940": true, "700950": false, "700960": true, "700970": true, "700980": true, "700710": true, "700990": true, "700800": true, "701000": true, "701010": true, "701020": true, "701030": true, "701040": true, "701050": true, "701060": true, "701070": true, "700720": true, "701080": true, "701090": true, "701100": true, "701110": true, "701120": true, "701130": true, "701140": true, "701150": true, "701160": true, "701170": true, "700730": true, "700740": true, "700750": true, "700760": true, "700770": true } } ][/spoiler] Putting aside whether or not Calcified Fragments really do taste like sticky pie (with a hint of victory), it should be very easy to see how to pull information about them from this list. It's [b]definitely worth noting[/b] that because the cardIds are numerically sequential, you can parse this object into JavaScript without having to worry about messing up the order if you happen to be storing extra information about Calcified Fragments using an index order (0-49). But if your JSON parser does respect the original order, you will need to check this because I don't believe the above is ordered based on the roman numeral of each fragment. On that note, here's my own list of fragments with basic location information on each one. [url]http://pastebin.com/UaR7X3v8[/url] Some of the really good guide websites include videos and screenshots and such, which takes a fair amount of effort to put together and keep up to date. But if you want to offer video guides without the hassle, there's another solution you can use. Grab yourself a [url=https://console.developers.google.com]Google API Key[/url] and check out the [url=https://developers.google.com/youtube/v3/docs/search/list]Youtube API Search[/url] page. Here's an example Search request: [quote]GET https://www.googleapis.com/youtube/v3/search?key={googleApiKey}&part=snippet&maxResults=10&q={query}[/quote] I found querying "Calcified Fragment V", where you replace "V" with the fragment roman numeral you want to look for returned pretty accurate results. Feed that into your output and you have video guides you don't have to update yourself (but aren't guaranteed to be 100% accurate all the time). If you see it getting a lot of hits, I'd suggest caching your search as Google APIs have a [url=https://developers.google.com/youtube/v3/getting-started#quota]quota limit[/url].