notes
Overview
| Name | notes |
| Type | Resource |
| Id | pagerduty.incidents.notes |
Fields
| Name | Datatype | Description |
|---|---|---|
id | string | |
channel | object | The means by which this Note was created. Has different formats depending on type. |
content | string | The note content |
created_at | string | The time at which the note was submitted |
user | object | The user who created a Note. If a service created this Note the user.type will be "bot_user_reference" and user.summary will list the name of the service rather than the user. |
Methods
| Name | Accessible by | Required Params | Description |
|---|---|---|---|
list_incident_notes | SELECT | id | List existing notes for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the API Concepts Document Scoped OAuth requires: incidents.read |
create_incident_note | INSERT | From, id, data__note | Create a new note for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. A maximum of 2000 notes can be added to an incident. For more information see the API Concepts Document Scoped OAuth requires: incidents.write |
_list_incident_notes | EXEC | id | List existing notes for the specified incident. An incident represents a problem or an issue that needs to be addressed and resolved. For more information see the API Concepts Document Scoped OAuth requires: incidents.read |