How to use API to connect agents

Have you looked at this page? Agents · solarwinds/OrionSDK Wiki · GitHub

Yes, I saw that page.  I learned enough C# yesterday to recognize that as C# code today.  What those calls generate for an API http{s} request (assuming that's what they do) will take me a long time floundering about the C# SDK code.  A structrural description of the code would be helpful, though I fear it's going to depend on many libraries I've never seen before (not having seen any C# libraries before).

That page uses C# notation to describe the verbs, but converting to a JSON payload is straightforward. If you have verb "VerbName" on entity "Orion.EntityName", then the URL to call it is /SolarWinds/InformationService/v3/Json/Invoke/Orion.EntityName/VerbName. Pass the argument values as a JSON array. So to deploy an agent to a Windows server, POST to /SolarWinds/InformationService/v3/Json/Invoke/Orion.AgentManagement.Agent/Deploy with a body like:

[ 1, 'display name for new node', 'myserver.local', '1.2.3.4', 'administrator', 'myP@ssw0rd' ]

I found this page: REST · solarwinds/OrionSDK Wiki · GitHub  enormously helpful in combination with the schema description - that's how I derived the "curl" code above.  The "deploy" and other verbs having to do with agents appear to have arguments not associated with table columns provided in the schema.  Thus, I don't know what they're named.

Could I just take the C# variable names and upcase the leading character to obtain the Json name?

I now see that the "Deploy" verb never takes AgentID as an argument.  My agents are already listening on port 17779 on my Linux boxes (installed by ansible+expect script); I'm trying to automate getting Solarwinds to talk to them; the curl code in OP creates the agent in SolarWinds, but does not tell Solarwinds to (or how to) connect to the agent; the Linux agents have a mandatory password, and that at a minimum would be part of the "connect to the agent" instructions.

Sorry, s/17779/17790/

Unfortunately, the agent management API does not support adding a connection to an existing agent. This lack is tracked as DC-1045 internally; I'll add your vote to it.

I understand this to mean the Json data should be sent as an array, with values in the order of the positional parameters of the C# call.  Let me know if I got that wrong.  Thanks!

That is correct.

Note for the future: starting with Orion Platform 2018.4 (NPM 12.4), currently in the release candidate stage, SWIS will also accept verb arguments in json object format. In this format, the names matter but the order does not. The json array format will still be accepted. I think the json object format will be more in keeping with how other REST APIs work, plus it allows for generating a Swagger/OpenAPI specification.

I was have the same problem...hundreds of pre-installed agents on servers to add into NPM.  So  I wrote a Powershell script that automates the browser actions.   See thwack.solarwinds.com/.../automating-addition-of-npm-nodes-with-pre-installed-agents----a-powershell-script-using-ie-automation