How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

SolarWinds Incidents API

Manage IT incidents

SolarWinds Incidents API is one of 31 APIs that SolarWinds publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Incidents. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, an API reference, and a getting-started guide.

This API exposes 5 operations across 2 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 2.1.

Requests are made against a single base URL, https://api.samanage.com.

5 operations 2 paths 5 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.1
Base URL
https://{orion-server}:17778/SolarWinds/InformationService/v3
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

SolarWinds Incidents API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — API token authentication via X-Samanage-Authorization header with Bearer prefix

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Incidents 5

Manage IT incidents

GET
/incidents.json
Solarwinds List Incidents
listIncidents 2 params → 200401
POST
/incidents.json
Solarwinds Create an Incident
createIncident body → 200400401
GET
/incidents/{id}.json
Solarwinds Get an Incident
getIncident 1 param → 200401404
PUT
/incidents/{id}.json
Solarwinds Update an Incident
updateIncident 1 param body → 200401404
DELETE
/incidents/{id}.json
Solarwinds Delete an Incident
deleteIncident 1 param → 200401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Incident (11 properties), UserRef (3 properties), CategoryRef (2 properties), IncidentCreate (1 property). Each schema is shown below with its type and property counts.

IncidentUpdate
object
1 property 1 required
IncidentCreate
object
1 property 1 required
CategoryRef
object
2 properties
UserRef
object
3 properties
Incident
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

solarwinds-incidents-api-openapi.yml Raw ↑

Other APIs SolarWinds publishes across the network.

SolarWinds Database Performance Analyzer API
SolarWinds NPM REST API
SolarWinds Web Help Desk API
SolarWinds IPAM API
SolarWinds NCM API
SolarWinds SAM API
SolarWinds AppOptics API
SolarWinds Account API
SolarWinds Assets API
SolarWinds BulkOperations API
SolarWinds Categories API
SolarWinds Changes API
Where this information came from

This is an independent, third-party profile of SolarWinds Incidents API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.