Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

How to do API scripting from SolarWinds application to integrate with other 3rd party applications

Hi Anyone,

Does anyone have any document of API scripting from SolarWinds application to integrate with other 3rd party applications

or is anyone aware how achieve this.

Find more posts tagged with

Accepted answers

All comments

bmallon

Which 3rd part apps are you looking to integrate with? Each app will be slightly different.

adam.beedell

I do this a bunch

This is waaaaaaaaay too big a question, take many steps back

Figure out what you want to do
Figure out what the components would be to achieve that
Figure out where you'd store stuff you need to store
Find the API support docs for each system
Find working creds for each system

Get network access working between the parts
Build stuff
Test stuff

Fix plan
Build stuff
Test Stuff
Move toward prod
Setup monitoring inc nulls
Set up visuals

etc

AdamRichards

@bmallon @adam.beedell

Can you give at least a brief overview how to even begin as I have similar question...

how do you even do a simple api call within sw like in a widget on a node details page for example

for example wanting to link to the node you're viewing in sw but on a 3rd party tool like netbrain or statseeker or liveaction/livenx

you could do a api call to those programs with the node caption or ip etc and grab their custom url for it. how would you do this in Solarwinds?

adam.beedell

Either assign a new api poller to a node and build that equivalent to postman, or you can use a https monitor component in an application template for some basic stuff, or you can do the same in a script monitor component for advanced stuff.

(Script components should exit in a solarwinds format described in other threads)