Skip to main content

API Coverage

Compare API endpoint support across different incident management platforms. This matrix shows which features are available for each integration.

Filter by capabilities

RESOURCEAuthServiceIncidentsTeam
Jira Service Management
ManageEngine ServiceDesk Plus
Opsgenie
PagerDuty
ServiceNow
SolarWinds
VictorOps

Field Mappings​

Our unified API standardizes data models across different incident management providers. Below you can see how Unizo fields map to provider-specific fields for each data model.

Organizations

Details about the organization’s identity and structure

Unizo Field
Jira Service Management
ManageEngine ServiceDesk Plus
Opsgenie
PagerDuty
ServiceNow
SolarWinds
VictorOps
idOrganization identifier
loginOrganization username
nameOrganization name
changeLogModification history

Services

Metadata and identifiers for registered services

Unizo Field
Jira Service Management
ManageEngine ServiceDesk Plus
Opsgenie
PagerDuty
ServiceNow
SolarWinds
VictorOps
idService identifier
nameService name
descriptionService description
teamResponsible team
urlService URL
changeLogModification history

Teams

Information about response or ownership teams

Unizo Field
Jira Service Management
ManageEngine ServiceDesk Plus
Opsgenie
PagerDuty
ServiceNow
SolarWinds
VictorOps
idTeam identifier
nameTeam name
descriptionTeam description
updatedAtUpdated date

Incidents

Details and tracking of reported incidents

Unizo Field
Jira Service Management
ManageEngine ServiceDesk Plus
Opsgenie
PagerDuty
ServiceNow
SolarWinds
VictorOps
idIncident identifier
nameIncident name
titleIncident title
login Login identifier
statusIncident status
priorityPriority level
descriptionIncident description
incidentKeyIncident key
createdByIncident creator
urlIncident URL
urgencyUrgency level
usernameCreator username
targetsAffected targets
projectProject information
servicePrimary service
isMultiResponderMultiple responders
teamResponse team
servicesAffected services
organization Organization info
changeLogModification history

Native Provider Field Support​

Leveraging nativeResponse​

The nativeResponse field enables you to access provider-specific features beyond our unified common data model. This feature allows you to:

  • Access provider-specific incident attributes not included in the common data model
  • Implement custom escalation workflows using native provider capabilities
  • Utilize advanced alerting features unique to each platform
  • Maintain compatibility with existing provider-specific integrations
Enterprise Feature

The nativeResponse field is available exclusively for Enterprise and Launch Customer subscriptions. Contact our sales team to upgrade your plan and unlock access to native provider data.

How to Use nativeResponse​

{
  "id": "inc-123",
  "title": "Database connection failure",
  "status": "triggered",
  "priority": "high",
  // ... other unified fields
  "nativeResponse": {
    // Complete provider-specific response
    "escalation_policy": {
      "id": "policy-456",
      "name": "Database Team Escalation"
    },
    "first_trigger_log_entry": {
      "type": "trigger_log_entry",
      "summary": "Triggered via monitoring integration"
    },
    "conference_bridge": {
      "conference_number": "+1-555-0123",
      "conference_url": "https://example.com/bridge/123"
    },
    "responder_requests": []
  }
}

Need Something More?​

Working on a unique incident management integration? Need extra fields for your alerting tools? We're here to help.

Get in touch:

We'd love to hear about your use case and help expand our API to meet your needs.