PagerDuty
PagerDuty is a cloud-based incident response platform that integrates with the PagerDuty REST API. You can bring service, team, user, and incident data from PagerDuty into Brinqa to gain a unified view of your attack surface, thus strengthening your cybersecurity posture.
This document details the information you must provide for the connector to authenticate with PagerDuty and how to obtain that information from PagerDuty. See create a data integration for step-by-step instructions on setting up the integration.
Required connection settings
When setting up a data integration, select PagerDuty from the Connector dropdown. If you cannot find the connector in the dropdown, make sure that you have installed it first. You must provide the following information to authenticate PagerDuty with Brinqa:
-
URL: The PagerDuty REST API base URL (e.g.,
https://api.pagerduty.com). -
Access Token: A PagerDuty API access token. The connector sends this token on every API request as an
Authorization: Token token=<accessToken>header.
Generate a PagerDuty API access token
For the PagerDuty connector to retrieve data from the PagerDuty API, you must provide a PagerDuty API access token. You can create a User token or a General Access Token from your PagerDuty account settings. For additional information, see PagerDuty API reference documentation.
Additional settings
The PagerDuty connector contains additional options for specific configuration:
- Page size: The maximum number of records to get per API request. The default setting is 100. It is not recommended to go over 100.
- Parallel requests: The maximum number of parallel API requests. The default setting is 4.
- Maximum retries: The maximum number of times that the integration attempts to connect to the PagerDuty API before giving up and reporting a failure. The default setting is 10.
Types of data to retrieve
The PagerDuty connector can retrieve the following types of data from the PagerDuty REST API:
Table 1: Data retrieved from PagerDuty
| Connector Object | Required | Maps to Data Model |
|---|---|---|
| Incident | No | Incident |
| Service | No | Application |
| Team | No | Team |
| User | No | Person |
The PagerDuty connector does not currently support operation options for the types of data it retrieves.
For detailed steps on how to view the data retrieved from PagerDuty in the Brinqa Platform, see How to view your data.
Attribute mappings
Expand the sections below to view the mappings between the source and the Brinqa data model attributes.
Incident
Table 2: Incident attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
IncidentResource.acknowledgements[].acknowledger.id | ACKNOWLEDGER_IDS |
IncidentResource.alert_counts.all | ALERTS_COUNT |
IncidentResource.assigned_via | ASSIGNED_VIA |
IncidentResource.assignments[].assignee.id | ASSIGNMENT_ASSIGNEE_IDS |
IncidentResource.body.details | BODY |
IncidentResource.body.type | BODY_TYPE |
IncidentResource.conference_bridge.conference_number | CONFERENCE_BRIDGE |
IncidentResource.created_at | SOURCE_CREATED_DATE |
IncidentResource.escalation_policy.id | ESCALATION_POLICY |
IncidentResource.first_trigger_log_entry.id | FIRST_TRIGGER_LOG_ENTRY |
IncidentResource.html_url | HTML_URL |
IncidentResource.id | UID |
IncidentResource.incident_key | INCIDENT_KEY |
IncidentResource.incident_number | INCIDENT_NUMBER |
IncidentResource.incidents_responders[].user.id | INCIDENT_RESPONDER |
IncidentResource.last_status_change_at | LAST_STATUS_CHANGE_AT |
IncidentResource.last_status_change_by.id | LAST_STATUS_CHANGE_BY |
IncidentResource.occurrence.count | OCCURRENCE |
IncidentResource.pending_actions[].type | PENDING_ACTIONS |
IncidentResource.priority.id | PRIORITY |
IncidentResource.resolve_reason.incident.id | RESOLVE_REASON_INCIDENT |
IncidentResource.resolve_reason.type | RESOLVE_REASON_TYPE |
IncidentResource.responder_requests[].requester.id | INCIDENT_REQUESTER |
IncidentResource.self | SELF |
IncidentResource.service.id | SERVICE_ID |
IncidentResource.status | STATUS |
IncidentResource.summary | SUMMARY |
IncidentResource.teams[].id | TEAM_IDS |
IncidentResource.title | TITLE |
IncidentResource.type | TYPE |
IncidentResource.urgency | URGENCY |
Service
Table 3: Service attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
ServiceResource.acknowledgement_timeout | ACKNOWLEDGMENT_TIMEOUT |
ServiceResource.addons[].id | ADDONS |
ServiceResource.alert_creation | ALERT_CREATION |
ServiceResource.alert_grouping | ALERT_GROUPING |
ServiceResource.alert_grouping_parameters.config | ALERT_GROUPING_PARAMETER |
ServiceResource.alert_grouping_timeout | ALERT_GROUPING_TIMEOUT |
ServiceResource.auto_pause_notifications_parameters.enabled | AUTO_PAUSE_NOTIFICATIONS |
ServiceResource.auto_resolve_timeout | AUTO_RESOLVE_TIMEOUT |
ServiceResource.created_at | SOURCE_CREATED_DATE |
ServiceResource.description | DESCRIPTION |
ServiceResource.escalation_policy.id | ESCALATION_POLICY |
ServiceResource.html_url | URL |
ServiceResource.id | UID |
ServiceResource.incident_urgency_rule.urgency | INCIDENT_URGENCY |
ServiceResource.integrations[].id | INTEGRATIONS |
ServiceResource.last_incident_timestamp | LAST_INCIDENT_TIMESTAMP |
ServiceResource.name | NAME |
ServiceResource.response_play.id | RESPONSE_PLAY |
ServiceResource.scheduled_actions[].type | SCHEDULED_ACTIONS |
ServiceResource.self | SELF |
ServiceResource.status | STATUS |
ServiceResource.summary | SUMMARY |
ServiceResource.support_hours.days_of_week | SUPPORT_HOURS_DAYS |
ServiceResource.support_hours.end_time | SUPPORT_HOURS_END_TIME |
ServiceResource.support_hours.start_time | SUPPORT_HOURS_START_TIME |
ServiceResource.support_hours.time_zone | SUPPORT_HOURS_TIME_ZONE |
ServiceResource.support_hours.type | SUPPORT_HOURS_TYPE |
ServiceResource.teams[].id | TEAM_IDS |
ServiceResource.updated_at | SOURCE_LAST_MODIFIED |
Team
Table 4: Team attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
TeamResource.default_role | DEFAULT_ROLE |
TeamResource.description | DESCRIPTION |
TeamResource.html_url | HTML_URL |
TeamResource.id | UID |
TeamResource.name | NAME |
TeamResource.parent.id | PARENT |
TeamResource.self | SELF |
TeamResource.summary | SUMMARY |
TeamResource.type | TEAM_TYPE |
User
Table 5: User attribute mappings
| Source Field Name | SDM Attribute |
|---|---|
UserResource.avatar_url | AVATAR_URL |
UserResource.billed | BILLED |
UserResource.color | COLOR |
UserResource.contact_methods[].id | CONTACT_METHODS |
UserResource.description | DESCRIPTION |
UserResource.email | EMAIL |
UserResource.html_url | HTML_URL |
UserResource.id | UID |
UserResource.invitation_sent | INVITATION_SENT |
UserResource.jobTitle | JOB_TITLE |
UserResource.name | NAME |
UserResource.notification_rules[].id | NOTIFICATION_RULES |
UserResource.role | ROLE |
UserResource.self | SELF |
UserResource.summary | SUMMARY |
UserResource.teams[].id | TEAMS |
UserResource.time_zone | TIMEZONE |
UserResource.type | USER_TYPE |
APIs
The PagerDuty connector uses the PagerDuty REST API v2. Specifically, it uses the following endpoints:
Table 6: PagerDuty API endpoints
| Connector Object | API Endpoint |
|---|---|
| Incident | GET /incidents |
| Service | GET /services |
| Team | GET /teams |
| User | GET /users |
Changelog
The PagerDuty connector has undergone the following changes:
Table 7: PagerDuty connector changelog
| Version | Description | Date Published |
|---|---|---|
| 3.0.0 | Improvements - Timestamp attributes ( LAST_STATUS_CHANGE_AT on Incident; SOURCE_CREATED_DATE and LAST_INCIDENT_TIMESTAMP on Service) are now returned as proper datetime values instead of numeric epoch milliseconds, enabling accurate time-based filtering and display. - Internal framework upgrade: models now use a shared connector base class, improving consistency and maintainability across the connector platform. Migration Required - 'Incident': LAST_STATUS_CHANGE_AT changed from a numeric epoch value (Long) to a datetime (Instant) — Action: re-sync - 'Service': SOURCE_CREATED_DATE and LAST_INCIDENT_TIMESTAMP changed from numeric epoch values (Long) to datetimes (Instant) — Action: re-sync | June 9th, 2026 |