originally posted in:BungieNetPlatformView Entire Topic
Apparently I need to be set straight because now my data is all wonky. Please help me. The intent here is notification of daily and weekly events. I have been pulling data to alert when special events like Iron Banner, Trials, Weekly Crucible, Xur start from the public advisors endpoint: https://www.bungie.net/platform/Destiny/Advisors/ Under there the events endpoint (['Response']['data']['events']['events']) really only provides Xur and Iron Banner. SO I end up checking Brother Vance for bounties to know if Trials has started. The weekly crucible usually has map data under it located at ['Response']['data']['weeklyCrucible'] but now it is empty and I presume it will stay that way until next Tuesday. However, the weekly is Inferno Clash 6v6. So the questions are: 1. How do I correctly find out when trials starts? 2. how do I correctly gather the weekly crucible? 3. What about when a special event happens like SRL or Crimson? Where should I pull that. 4. If these are special events (Trials, SRL, C.Days) why do they not have an entry in the events endpoint feed? Is it because they take over the Weekly Crucible spot in the director? IMHO, I would think this would be easier from both a programming and UI perspective if there were a dedicated octagon on the director for these special events (not Xur obviously), which could lead to consistency within the advisors feed. Obviously this is an over simplification and one really does not correlate to the other, but couldn't all the special events such as I.B., SRL, CD, etc. become lists under the events feed?
Greetings! Yes, so it sounds like you've got two separate issues here: 1) Various events (trials, SRL, Crimson etc...) aren't defined as Events in the Events endpoint 2) Weekly Crucible data isn't being returned I'll have to investigate (2) - you should be getting data for that, so there could be an error in our configuration of weekly crucible information! We'll look into it! But for (1) it's a bit of a long story. The events endpoint is something that we would manually configure when we needed information to come down that endpoint: we used it to drive certain UI in the mobile applications, and we used to use it for some old elements on the BNet website that have since been deprecated. Many events that were once driven by fixed calendars are now manually configured, so the information about those events are less interesting (as, for example, we can't know via content when a certain event is going to end, only that it's currently active or inactive). We can manually configure when we're told these events are going to end, but it is potentially subject to change and thus the data would be relatively unreliable. Since we've not been using the Events endpoint lately, it has been left neglected for some time now. I will bring it up - though we wouldn't be able to give you some useful information like the specific date that these events are ending in many cases, it would be useful to continue populating that events data for your guys' purpose even though we personally don't use it anymore.