Provide a public Xur API #502
Comments
|
This would be very helpful! To display Xur listings on destinysets.com to unauthenticated users, I have to run my own Xur API, which a couple of other people use as well. Problem is maintenance and uptime isn't my strong suit, so it would be great if I didn't have to worry about this any more. |
|
yes please! |
|
So there is no way i can get xur inventory without asking users to authenticate? |
|
This would be really nice for bots and the like (really, accessing any vendor), especially given how cumbersome the oauth flow is |
|
Yes, I agree! With Triumphs and Forsaken work, this has had to take a back seat for the time being: but it is on our backlog! |
|
Awesome!! Our future Xur bots thank you :) |
|
This should probably include all vendors, not just Xur. It'd be good if you could specify which vendors you want to return depending on your needs. |
|
Because of his not specific to a charter nature and the event like status he held, could this not be part of a public vendors endpoint? |
|
Does the latest TWAB nullify any of these plans? |
|
Still to be determined on the endpoint overall - but one way or another, I won't be allowed to return destination information for him. |
|
so in other words, there will be no chance to get his position by API ? we have to wait till some youtuber finished his search for him ? 🤔 😖 |
|
Sorry guys - design decisions overrule my preference for more data. |
|
But sales data will all be there still?
Get Outlook for iOS<https://aka.ms/o0ukef>
…________________________________
From: Vendal Thornheart <notifications@github.com>
Sent: Saturday, August 25, 2018 3:25:28 AM
To: Bungie-net/api
Cc: Tom Chapman; Comment
Subject: Re: [Bungie-net/api] Provide a public Xur API (#502)
Sorry guys - design decisions overrule my preference for more data.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#502 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AAJkCc99HVz1S6WO4VQ8SCiJwnwGnD3Gks5uUDcIgaJpZM4ULoci>.
|
|
Yeah, all of that will still be there in the existing Vendors endpoint. Still TBD on the idea of having a public Xur endpoint though. |
|
All good, thanks for keeping us updated. 👍 |
|
A couple of us in the community were talking about setting up an endpoint for returning his current location based on a manual dataset I will probably set up and maintain as part of my maps project. Assuming there are a finite number of locations for him to be in, eventually we will have a complete dataset and just need to specify which id is active. I'll probably make a direct link for the maps along the lines of The one hiccup is that reset now happens at 3.30am for me, so I won't be able to update the current location in a timely manner. |
|
maybe the rss feed of findxur.com is a reasonably good solution, until someone provides a real api 🤔 |
|
hi all, since finxur.com seems to be down or broken, i am really searching for a reliable source to get this info. is anybody planing something here ? maybe we can create a community build API for this, where the users can report xur´s location with one single click. based on the number of clicks by location, we could take this info as (most) correct info. on the other hand, we could select some public websites and grep the info from there, as soon as it´s available. |
https://braytech.org/creators/ and our friend @justrealmilk |
|
@mattybeard nope... braytach changed, the xur api no longer is working, oh boy, this is so stupid of bungie that people have to search for xur´s location every f... week 😠 every stupid friday i need to search google to find his location instead of using the bungie api 😕 |
|
Lets keep our comments polite and friendly here, Bungie is providing us with a huge service by allowing us to use their APIs, and even so much as officially supporting them this time around, so lets keep things friendly! |
|
@mattybeard friend! |
|
@justrealmilk i guess you don´t have to be awake for that ;) i have a cronjob myself that starts severel times after xurs location should be visible. i searched a few blogs that could be parsed easily (the html dom) - now i have found another one that works, as long they use the same layout. the point is: yes, nobody cares about xurs and his boring old stuff. for me it´s only a part that belongs to the weekly stuff where i notify my community about changes. most don´t care about xur, but some do. it´s annyoing that some things never found their way to the api, like the calus raid counter order, which weapons you can get on the EP this week. the community always has to find workarounds for this stupid things, that are important to many players. that´s why i asked here: maybe it´s an idea to create a public api for everybody with infos, bungie is unable to provide, accessable for every developer, managed by the community. it´s just an idea..... |
|
To clarify something, Bungie isn’t unable — Bungie is _unwilling_.
Thorn indicated that game designers consciously removed Xûr’s map icon in-game and prohibited exposing Xûr’s location in the API.
Please remember to be respectful of Bungie’s choices. Their choices on “how important are API checkpoints to fix” and “whether or not to show Xûr’s location at all” may be unpalatable, but that’s no reason to call their decisions “stupid things”.
… On Nov 11, 2018, at 10:52, Michael Bladowski ***@***.***> wrote:
@justrealmilk i guess you don´t have to be awake for that ;) i have a cronjob myself that starts severel times after xurs location should be visible. i searched a few blogs that could be parsed easily (the html dom) - now i have found another one that works, as long they use the same layout. the point is: yes, nobody cares about xurs and his boring old stuff. for me it´s only a part that belongs to the weekly stuff where i notify my community about changes. most don´t care about xur, but some do. it´s annyoing that some things never found their way to the api, like the calus raid counter order, which weapons you can get on the EP this week. the community always has to find workarounds for this stupid things, that are important to many players.
that´s why i asked here: maybe it´s an idea to create a public api for everybody with infos, bungie is unable to provide, accessable for every developer, managed by the community.
it´s just an idea.....
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
|
@michabbb, @floatingatoll I don't think he's calling Bungie's decision stupid, but rather, the circumstance we find ourselves in. This is less about Xur, and more about the vendor endpoint requiring auth in general. My understanding, from what I've gleaned from @vthornheart-bng, is that the endpoint is super intertwined with our systems, and while there are some should we at all and how should we decisions, the technical complexities that rise from separating the endpoints from its complicated internal web versus priority of requests is what really keeps use from getting a public endpoint for xur. People like me exist though. https://api.braytech.org/?request=xur&get=history |
|
@vthornheart-bng‘s reply above explicitly says that the game designers have prohibited the official API from publishing Xûr’s location: |
|
I said nothing of his location 🙈 |
|
In two previous replies in this thread you specifically talked about location and being disappointed in Bungie for withholding it. I apologize for confusing your prior comments on this specific issue with your most recent comments on this specific issue, and will mute and exit this thread immediately. |
|
Ah, you're talking about the fact that we don't have a public Xur endpoint rather than the location info? In that situation, it's a matter of the time that we have vs. the higher priority work that we have to get to. In the end, you're talking right now to the only person actively working on the Destiny API. Whatever I have the ability to do in my workday is what gets done in the API: that's balanced between
The public Xur endpoint is something I want to provide! I haven't had time to work on it yet, but it is something I would personally put high on the winter wishlist - so hopefully we can make it happen during the upcoming holiday season! (But just to note, it won't have location no matter what: indeed I have been asked not to return that information) |
|
oh boy, I thought it would be allowed to say what you think, but it seems that you are complaining about the choice of words rather than constructive suggestions. i´m out. thanks. |
|
Hey y'all, let's all be little Fonzies here. No need to fight - it's easy to misinterpret what people say/people's intent on the internet, and for that to snowball. |
Confused about this. Surely determining the location of Xur is, like, really easy? As in, just look at where the flashpoint is and go to the same position as he always is on that planet? Why not include that information? Also any update to this? I don't think @justrealmilk 's braytech.org api has been updated in a while so this would be real useful about now. |
|
@VeraxonHD Xur isn’t tied to flashpoint any longer. As for my private endpoint, I don’t personally use it at this point and as I have no insights as to its use by others, I find it really difficult to feel invested in maintaining it. |
Ah, right, of course.
I used it, for lack of any other alternative, and it was really helpful considering I haven't the time to boot up the game and enter it manually. But that's understantable. |
|
Aye, I was specifically asked not to return location information in the endpoint unfortunately. I know that's a bummer for those who use it - sorry that I can't provide it! Now that it's the week between Christmas and New Year's, I finally have some time to carve out for winter wishlist work. This one's the next one down in my hit list! I'll let you know when I've got something ready, and the details of what it is. |
|
TFS 330631, filed ages ago and long left in the dark corner of our backlog |
vthornheart-bng
added
the
bug filed
|
Okay, so after a bit of hassle trying to find a more generic way to potentially return more information than just Xur, I found that character-agnostic Vendor information is even hairier now than I realized. I'm going to return just Xur from this endpoint, who is currently the only vendor that I'm certain doesn't have meaningful character-specific sale items. Someday I'd like to talk more on the subject, but I fear if I did that I'd go too deep into the secret sauce. I'd likely be summarily executed. Anyways, this is ready for the January deployment - but for the forseeable future it will only have Xur in it. Which I guess is all anyone wanted, but I was personally hoping for more. Oh well. |
|
This should be fixed as of today's deployment (1/29)! |
It has been requested that we revive the old public Xur API! I think that's a good idea, let's do that when we get the time.
The text was updated successfully, but these errors were encountered: