Ah, the unlock mechanism is a new one that isn’t picked up by my content reading bits.
Not sure when I’ll have that fixed.
Huh, that’s super strange. Not sure why it’s broken, will have to look into that.
https://api.guildwars2.com/v2/titles?ids=all is returning “all ids are invalid” for you? It’s returning all the title data without error for me.
Some new achievements are not returned from the API. For example, I have this achievement: https://api.guildwars2.com/v2/achievements?ids=3843
I noticed this issue here: https://metagamerscore.com/forum_topics/5086
That achievement doesn’t have any data (name/description/etc), nor does it award any AP. It’s probably just a content artifact. There isn’t currently a way to blacklist achievements on the API, but if I had time I’d blacklist it so it’s not being returned from that endpoint.
Just added it.
Can API endpoint be improved to be more usable – approaching real time updates?
The delay is caused by two things:
- The map instance servers only persist character data back to the database periodically (once every few minutes), not in real-time.
* Since the API backend talks directly to the character database, it caches data (five minutes) to avoid setting the entire game on fire.
Because of the first reason, primarily, real-time updates are architecturally impossible.
Nope to both questions.
I might have this by the end of the week? Added it in yesterday, need to integrate the change out to live and deploy.
Was considering adding a second field, “accesses” or something that’s just an array.
Really not a fan of the comma separated list, but it’s probably the more backwards-compatible approach.
Should be up sometime today.
Forgot to go through the whitelist yesterday.
All the achievements unlocked so far should be blessed.
Sorry, just got in.
We had a hardware failure that we’re working to resolve.
EDIT: The failure was in the Frankfurt datacenter, so if you route your requests to Dallas (via 64.25.40.51) they should start working again.
EDIT2: Things should be coming back online now. Sorry about the mess!
(edited by Lawton Campbell.8517)
Pagination no longer an option?
It’s on the table but I’m not sure when I’ll have time to implement it.
Turned it on without announce in case I had to turn it back off again.
It’s probably never going to work with those accounts, unfortunately.
Any update on this issue? It has been going on for over 3 months now
I thought I’d fixed it, but I guess the fix didn’t work with non-dev content.
I haven’t had much time recently to work on API stuff, unfortunately.
No. The ?top parameter comes kind of close, but it sorts by price, not quantity.
Assuming you’re talking about materials in character inventories; does requesting the data manually from the API work? If you get “https://api.guildwars2.com/v2/characters/CHAR-NAME/inventory?access_token=API-KEY”, does it show the inventory contents? If it does, it’s likely that the problem is on gw2crafts.net. I’m guessing that site only inspects your material storage.
Fair. Here’s a tracking issue.
Seems reasonable. Here’s a tracking issue. Not sure if/when I’ll have time to implement it.
The vendor value of item 36332 is 0, which AFAIK makes the item implicitly untradeable. I believe the API is correct (and attempts to purchase it via the TP should fail, regardless of what the UI displays).
There’s an open issue for this but I’m not sure if/when I’ll have time to implement it
There’s some performance issues with /v2/commerce/delivery — so I’m disabling it until those can be sorted out. Expect it to be disabled for a few weeks, unfortunately.
Whoops, that’s one of the many manual bits.
I’ll update the configs in a minute.
Doing a bulk search, such as https://api.guildwars2.com/v2/items/?ids=12345,12346,12347,12348,12349 returns “301 Moved Permanently” and then redirects to https://api.guildwars2.com/v2/items/
You’ve got a stray “/” before the “?”. Use this URL instead: https://api.guildwars2.com/v2/items?ids=12345,12346,12347,12348,12349
Cat #30 wasn’t ever released.
I’ll remove it from the list at some point.
The areas you’re looking for are called sectors; they’re a sub-element of maps and can be retrieved e.g. via https://api.guildwars2.com/v2/continents/1/floors/1/regions/1/maps/31/sectors/233
The vendors, as described in the pull request, barely has any localized data. A “vendor” isn’t the NPC, it’s just the window with the items for sale. The main goals for the vendors endpoint were (1) to expose item pricing and (2) to expose rotating/daily vendor sales. There might be room in the future to provide a list of NPCs on each map (or in each sector) but that’s a much more difficult proposition (since a lot of NPCs are spawned via map scripts and so forth).
By default, yeah. The vendor prices can be overridden on a vendor-by-vendor basis. There’s a vendor endpoint that’s not available yet that (kind of) exposes the actual prices.
They seem to be listed currently.
Opened an issue for the WvW objectives overlapping.
This is the proposed change which I’ve got in the works. Had to push it back a release because one of the backend components — the bit that handles vendor whitelisting — didn’t get deployed (whoops).
Tracking issue. I actually had plans to implement something like that a couple of years ago; I don’t recall what exactly the blocker was.
I’m not entirely sure that match data is stored in a way that’s queryable on a per-arena basis (e.g., there’s no index to query match histories by arena); due to the way our backend system is structured adding an index is fairly infeasible for me. Will have to do some digging.
I opened a tracking issue for this. The main blocker is that our caching layer doesn’t actually expose the remaining duration for cache entries. Since the caching bit is very widely used throughout the game systems, modifying it is kind of scary.
Actually, I don’t know why I didn’t think of this sooner, but I can just wrap the cached objects in a wrapper that includes the cache timing information. It won’t be 100% accurate (clock sync) but it should be correct within a few seconds, hmm.
The build id only goes up when there’s a new patch available to download.
+1 to using it as a flag to expire any caches of /v2/items etc that you’ve got locally. That’s the ideal implementation, I think.
In the .equipment section of /v2/characters, there should be a .stats field on any items which have choosy-stats. stats.id references /v2/itemstats, and stats.attributes is the itemstats multipliers applied to the item’s level+type+rarity for the absolute stats (rather than just the multipliers).
There were a couple of blips about an hour ago due to network connectivity, but aside from that I dunno. I’m not seeing any issues on my end; you could manually check
https://api.guildwars2.com/v2/account?access_token=1234-API-KEY-HERE-6789
to see if any errors are returned. There’s definitely a lurking bug or two that can cause an error to be persistently returned for an account — really not sure what causes it but I suspect it’s triggered by transferring across NA/EU.
…huh.
I’ve raised the issue with the PvP team; they agree that the scores are swapped (but the results are correct). In the meanwhile, I’m going to add some code to the API frontend that tries to swap the scores back if it thinks they’re reversed.
Ah, okay, that makes sense.
I actually don’t recall the details. Is it only season 4 that has the rating, or do earlier seasons also have it? I think we’ve always tracked an internal MMR for matchmaking, but it wasn’t exposed via API until we started displaying the value in-game. The current implementation will emit a rating/decay value if it exists in the backend server, so I guess those old previously internal MMRs are visible.
I’ll add a note to the docs.
I’ll have to look into adding that; I’m not entirely sure how placed decorations are stored, will have to look into that. I’ve opened a tracking issue for it in the meanwhile.
Huh, the decay value should be in there; I’ll try to get that fixed. Tracking issue.
Does the API data differ from what’s displayed in the small match history bit in-game PvP panel?
I… I should add that in today.
There isn’t really much to expose; the cats endpoint works with a set of hardcoded name/id pairs. There isn’t any structured data that could be reasonably be provided.
If an endpoint that just lists all the name/id pairs meets your needs, I’ll go ahead and add it. It should be noted that it’ll be a week or so out-of-date when new cats come out since I usually forget.
EDIT: Tracking issue.
(edited by Lawton Campbell.8517)
I don’t have enough coffee in me yet to think, but this seems reasonable. I’ve opened a tracking issue for it.
Color me totally confused
Phew, glad this was something simple. There’s at least a couple lurking bugs in the API’s achievement bits and I was fearing for the worst!
So, two bits.
Daily achievements (well, all non-permanent achievements) don’t currently show up in /v2/account/achievements. There’s an open issue for this but I’m not sure when I’ll have time to implement it.
Using the ?ids parameter basically just returns a subset of all the account’s achievements — it won’t return anything that isn’t available when no parameters are provided. If the achievement ids don’t show up via just /v2/account/achievements, the API doesn’t think you have them.
Given the Flashpoint achievements are all permanent, it’s not clear to me why the API wouldn’t return them (unless you have no progress towards them?). Could you PM me the API key you’re using? I’d like to take a look and see if I can figure out what’s going on.
Added it to the hardcoded list; will start showing up the next time I do a deploy.
I should probably figure out a better way to maintain that :/
It’s not currently possible, but opened a tracking issue. There’s a few difficulties with the implementation that are probably going to make it not update correctly when you’re logged in (or might cause it to only update when you’re logged in, not entirely sure yet), so I’ve kind of been punting on it.
There’s an open issue for this, but it hasn’t been deployed yet. I actually don’t remember what the blocker for it was. Unfortunately it won’t show placed decorations, but it’ll show what’s in storage.