business_services
Overview
| Name | business_services |
| Type | Resource |
| Id | pagerduty.business_services.business_services |
Fields
| Name | Datatype | Description |
|---|---|---|
id | string | |
name | string | The name of the business service. |
description | string | The user-provided description of the business service. |
html_url | string | a URL at which the entity is uniquely displayed in the Web app |
point_of_contact | string | The point of contact assigned to this service. |
self | string | the API show URL at which the object is accessible |
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. |
team | object | Reference to the team that owns the business service. |
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. |
Methods
| Name | Accessible by | Required Params | Description |
|---|---|---|---|
get_business_service | SELECT | id | Get details about an existing Business Service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.read |
list_business_services | SELECT | List existing Business Services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.read | |
create_business_service | INSERT | Create a new Business Service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. There is a limit of 5,000 business services per account. If the limit is reached, the API will respond with an error. For more information see the API Concepts Document Scoped OAuth requires: services.write | |
delete_business_service | DELETE | id | Delete an existing Business Service. Once the service is deleted, it will not be accessible from the web UI and new incidents won't be able to be created for this service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.write |
_get_business_service | EXEC | id | Get details about an existing Business Service. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.read |
_list_business_services | EXEC | List existing Business Services. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.read | |
update_business_service | EXEC | id | Update an existing Business Service. NOTE that this endpoint also accepts the PATCH verb. Business services model capabilities that span multiple technical services and that may be owned by several different teams. For more information see the API Concepts Document Scoped OAuth requires: services.write |