Multiple conduit_socket entries for the same tier returned on soulbinds endpoint

Hello, just wanted to report an issue with the soulbinds endpoint.

Sample: (NoLinksAllowed)://eu.api.blizzard.com/profile/wow/character/eredar/araseses/soulbinds?namespace=profile-eu&locale=en_US

In the data there are 3 tier 1 conduit_socket entries where only 1 (the active one) is expected:

{
    "conduit_socket": {
        "type": {
            "type": "POTENCY",
            "name": "Potency Conduit Slot"
        },
        "socket": {
            "conduit": {
                "key": {
                    "href": "..."
                },
                "name": "Incessant Hunter",
                "id": 266
            },
            "rank": 2
        }
    },
    "tier": 1,
    "display_order": 0
},
{
    "conduit_socket": {
        "type": {
            "type": "ENDURANCE",
            "name": "Endurance Conduit Slot"
        },
        "socket": {
            "conduit": {
                "key": {
                    "href": "..."
                },
                "name": "Innate Resolve",
                "id": 256
            },
            "rank": 1
        }
    },
    "tier": 1,
    "display_order": 1
},
{
    "conduit_socket": {
        "type": {
            "type": "FINESSE",
            "name": "Finesse Conduit Slot"
        },
        "socket": {
            "conduit": {
                "key": {
                    "href": "..."
                },
                "name": "Born Anew",
                "id": 258
            },
            "rank": 3
        }
    },
    "tier": 1,
    "display_order": 2
},
...
1 Like

I just encountered this as well. The endpoint should either return only 1 (the selected) conduit/trait from each tier or each entry should have an active field indicating if the player selected a conduit/trait from that tier.

Hi all,

Thank you for the report. We are additionally tracking this report here: WoW Shadowlands API Update - Covenants, Soulbinds & More - #14 by Maguthul-11152.