Original Url: http://forum-en.guildwars2.com/forum/community/api/WvW-World-Linking

cyanfish.9521:

How will the upcoming world linking affect the WvW APIs? Are there any changes to the APIs planned for this?

Chaba.5410:

I hope so!

Need to be able to query the API for which worlds are linked together in a match. This will help out TS admins greatly! TY.

Lawton Campbell.8517:

Proposed changes are detailed here. Will almost certainly make all_worlds always there if only to make it easier for testing; should have that bit out today/tomorrow.

cyanfish.9521:

Looks good, thanks.

fro.8967:

Will this be launching before the world linking reset tonight?

Lawton Campbell.8517:

Already live for EU matchups.

Also I’d recommend using the /v2/wvw/matches?world=X query to get the match state (rather than enumerating all_worlds).

wanted.6214:

I tried to get the server id linked but didn’t work now.

For example, Far Shiverpeaks is linked to Underworld but in the api under “all_words” the id of Underworld missing.

https://api.guildwars2.com/v2/wvw/matches?world=2007

{
    red: 2014,
    blue: 2007,
    green: 2207
},
all_worlds: {
    red: [
        2014
    ],
    blue: [
        2007
    ],
    green: [
        2207
    ]
},

MentalFS.2589:

I’m getting the same now, although it worked yesterday after the reset.

NA worlds seem to be returned correctly, but EU worlds only have one world per color.

Tiscan.8345:

wanted.6214:

I tried to get the server id linked but didn’t work now.

Just checked it after i saw that my website is missing some data. Seems like the linked worlds are missing for all EU matchups (NA seems to be working!?).

The funny thing is that EU-matchups were correct yesterday evening.

Lawton Campbell.8517:

Oof, I’ll have the EU data fixed today. Sorry about that

wanted.6214:

Lawton Campbell.8517:

Oof, I’ll have the EU data fixed today. Sorry about that

Ty for the answer.

Lawton Campbell.8517:

Just pushed out a terrible fix which hardcodes the world links. The API should be now be returning the correct data.

The WvW endpoints might be a bit flaky today; we’re adjusting some stuff on the API backend to compensate for a significant increase in request volume (normally is 4k requests/minute; was up to 6k requests/minute this morning). Will keep y’all updated.

Sorry for the hassle

EDIT: Adjustments are finished and everything seems stable. I’ll keep a close eye on it over the weekend to make sure no additional shenanigans happen.