API Coverage

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

RESOURCE	Incident	Team	Team Members	Service	User	OnCall	Schedule
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.

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

Team Members

Response or ownership team members

Unizo Field	Jira Service Management	ManageEngine ServiceDesk Plus	Opsgenie	PagerDuty	ServiceNow	SolarWinds	VictorOps
idTeam member identifier
statusActive when user is in members list
user.idUser identifier
user.nameUser display name
user.emailUser email address
user.webUrlUser profile URL
team.idTeam identifier
team.nameTeam name
team.webUrlTeam URL
membership.roleMember role in team
changeLog.createdDateTimeRecord creation timestamp
changeLog.updatedDateTimeRecord last updated timestamp

Service

Metadata and identifiers for registered services

Unizo Field	Jira Service Management	ManageEngine ServiceDesk Plus	Opsgenie	PagerDuty	ServiceNow	SolarWinds	VictorOps
idUnique identifier for the service.
nameName of the service
descriptionBrief explanation of the service.
teamIdIdentifier for the team associated with the service.
urlURL or endpoint related to the service
created_atCreated Timestamp
updated_atUpdated Timestamp
native_responsePayload of respective provider

User

User and contact information for incident response

Unizo Field	Jira Service Management	ManageEngine ServiceDesk Plus	Opsgenie	PagerDuty	ServiceNow	SolarWinds	VictorOps
idUser identifier
nameUser display name
usernameUsername (derived from email when not provided)
emailUser email address
statusUser status (active, suspended, or inactive)
mobileMobile phone number
teams[].idTeam identifier
teams[].nameTeam name
teams[].webUrlTeam URL
role[].idRole identifier
role[].nameRole name
role[].descriptionRole description
webUrlUser profile URL
changeLog.createdDateTimeRecord creation timestamp
changeLog.updatedDateTimeRecord last updated timestamp

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

OnCall

On-call schedules and escalation policies

Unizo Field	Jira Service Management	ManageEngine ServiceDesk Plus	Opsgenie	PagerDuty	ServiceNow	SolarWinds	VictorOps
user.idOn-call user identifier
user.nameOn-call user name
user.webUrlOn-call user profile URL
schedule.idSchedule identifier
schedule.nameSchedule name
schedule.webUrlSchedule URL
escalation.policyIdEscalation policy identifier
escalation.levelEscalation level
timeWindow.startDateTimeOn-call period start
timeWindow.endDateTimeOn-call period end
changeLog.createdDateTimeRecord creation timestamp
changeLog.updatedDateTimeRecord last updated timestamp

Schedule

Schedule Management (Incident Management) – common attributes for PagerDuty & OpsGenie

Unizo Field	Jira Service Management	ManageEngine ServiceDesk Plus	Opsgenie	PagerDuty	ServiceNow	SolarWinds	VictorOps
idSchedule identifier
nameSchedule name
descriptionSchedule description
timeZoneSchedule time zone
enabledSchedule enabled flag
webUrlSchedule URL
owner.idOwner identifier
owner.nameOwner name
owner.webUrlOwner URL
rotations[].idRotation identifier
rotations[].nameRotation name
rotations[].startDateRotation start date/time
rotations[].endDateRotation end date/time
rotations[].coveragePercentageRotation coverage percentage
handoff.typeHandoff type
handoff.intervalHandoff interval
handoff.intervalSecondsHandoff interval in seconds
participants[].typeParticipant type
participants[].idParticipant identifier
participants[].nameParticipant name
participants[].emailParticipant email
participants[].webUrlParticipant profile URL
timeRestriction.typeTime restriction type
timeRestriction.restrictionTime restriction (daily)
timeRestriction.restrictionsTime restriction (weekly)
restriction.startHourDaily restriction start hour
restriction.startMinDaily restriction start minute
restriction.endHourDaily restriction end hour
restriction.endMinDaily restriction end minute
restriction.durationSecondsDaily restriction duration in seconds
restrictions[].startDayWeekly restriction start day
restrictions[].startHourWeekly restriction start hour
restrictions[].startMinWeekly restriction start minute
restrictions[].endDayWeekly restriction end day
restrictions[].endHourWeekly restriction end hour
restrictions[].endMinWeekly restriction end minute
restrictions[].startDayOfWeekWeekly restriction start day of week
metadata.providerProvider identifier
metadata.providerIdProvider schedule ID
metadata.selfUrlSelf URL

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:

Email: support@unizo.ai
Web: Contact Us

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

Filter by capabilities

Field Mappings​