Get Device Neighbors

@Carsten.Schmidt  It looks like a bug, I will create an internal bug to track it.

I tested another API, it works well. Could you have a try this one:

https://github.com/NetBrainAPI/NetBrain-REST-API-R10/blob/master/REST%20APIs%20Documentation/Topology%20Management/Get%20Device%20Neighbors%20by%20Topology%20Type%20API%20Version_1.md

@Gerry.zhang this is not a bug. The interface provided is only of the neighbouring device. In the RESTAPI documentation it is the same. The response documentation and the example confirm this:

I would like to see the interface of the queried device where the neighbour is connected to.

{'neighbors': [{'hostname': 'R4', 'interface': 'Ethernet0/1 123.10.1.1/30'}, {'hostname': 'R5', 'interface': 'Ethernet0/1 123.10.1.6/30'}], 'statusCode': 790200, 'statusDescription': 'Success.'}

@Carsten.Schmidt  Please see above link, the script is a little different, it provides the local interfaces.

{
    "topology":
    [
        {   
            "hostname": "device_1",
            "neighbors":
            [
                {
                    "interface": "intf_1",
                    "connected_device":
                    {
                        "nbr_device": "device_2",
                        "nbr_intf": "intf_3"
                    },
                    "topology": "L2"
                }
                {
                    "interface": "intf_2",
                    "connected_device":
                    {
                        "nbr_device": "device_3",
                        "nbr_intf": "intf_4"
                    },
                    "topology": "L2"
                }
            ]
        }
        {   
            "hostname": "device_4",
            "neighbors":
            [
                {
                    "interface": "intf_5",
                    "connected_device":
                    {
                        "nbr_device": "device_5",
                        "nbr_intf": "intf_6"
                    },
                    "topology": "L3"
                }
        }
    ]
}
 

@Gerry.zhang That fixed it, thank you very much!

Glad to hear that!