Just checked the source code, it seems to create a new extclient object, set its Network and IngressGatewayID parameters, then pass it to logic.CreateExtClient which in turn sees that it has no name & generates one for it

Thanks for the PR!

It was pretty trivial, but I thought it might help 😀

don't think it will work, client-id is not part of the route for createExtClient api endpoint

But the client-id is already a field in the json data

r.HandleFunc("/api/extclients/{network}/{nodeid}", securityCheck(false, http.HandlerFunc(createExtClient))).Methods("POST") .... .there is no clientid in this route

I'm probably missing something - Why is that an issue? Can't we use the clientid from the call's body?

yes, you can but you have to unmarhal it into a structure ... param read param from the url

Oh, I guess I misunderstood it then

take a look at the code for updateExtClient and how the newExtClient is decoded from the body

Is json.NewDecoder(input).Decode(C) Sort of like manually setting: C.clientid = input["clientid"] C.description = input["description"] And so on?