integrations
Overview
Name | integrations |
Type | Resource |
Id | pagerduty.services.integrations |
Fields
Name | Datatype | Description |
---|---|---|
id | string | |
name | string | The name of this integration. |
_type | string | |
created_at | string | The date/time when this integration was created. |
email_filter_mode | string | Specify for generic_email_inbound_integration. May override email_incident_creation |
email_filters | array | Specify for generic_email_inbound_integration. |
email_incident_creation | string | Specify for generic_email_inbound_integration |
email_parsers | array | Specify for generic_email_inbound_integration. |
email_parsing_fallback | string | Specify for generic_email_inbound_integration. |
html_url | string | a URL at which the entity is uniquely displayed in the Web app |
integration_email | string | Specify for generic_email_inbound_integration. Must be set to an email address @your-subdomain.pagerduty.com |
self | string | the API show URL at which the object is accessible |
service | object | |
summary | string | A short-form, server-generated string that provides succinct, important information about an object suitable for primary labeling of an entity in a client. In many cases, this will be identical to name , though it is not intended to be an identifier. |
type | string | A string that determines the schema of the object. This must be the standard name for the entity, suffixed by _reference if the object is a reference. |
vendor | object |
Methods
Name | Accessible by | Required Params | Description |
---|---|---|---|
get_service_integration | SELECT | id, integration_id | Get details about an integration belonging to a service. A service may represent an application, component, or team you wish to open incidents against. For more information see the API Concepts Document Scoped OAuth requires: services.read |
create_service_integration | INSERT | id, data__integration | Create a new integration belonging to a Service. A service may represent an application, component, or team you wish to open incidents against. For more information see the API Concepts Document Scoped OAuth requires: services.write |
_get_service_integration | EXEC | id, integration_id | Get details about an integration belonging to a service. A service may represent an application, component, or team you wish to open incidents against. For more information see the API Concepts Document Scoped OAuth requires: services.read |
update_service_integration | EXEC | id, integration_id, data__integration | Update an integration belonging to a Service. A service may represent an application, component, or team you wish to open incidents against. For more information see the API Concepts Document Scoped OAuth requires: services.write |