Atlassian: Add notifications to notification scheme

← Issue notification schemes operations · Get started

Operation atlassian.addnotifications

Provider route: PUT /{cloudId}/rest/api/3/notificationscheme/{id}/notification. Alter supplies the connection’s credentials and routing.

Call through Alter

Install @alter-ai/sdk @alter-ai/atlassian with npm, or alter-sdk-atlassian with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { AtlassianIntegration } from "@alter-ai/atlassian";

async function execute(input: Parameters<AtlassianIntegration["issueNotificationSchemes"]["addNotifications"]>[0]) {
  const app = new App({ apiKey: process.env.ALTER_API_KEY! });
  try {
    const provider = new AtlassianIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
    const call = await provider.issueNotificationSchemes.addNotifications(input);
    const result = await call.wait();
    return result.bodyJson();
  } finally {
    await app.close();
  }
}

import os
from alter_sdk import App
from alter_sdk_atlassian import AtlassianIntegration

async def execute(arguments):
    async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
        provider = AtlassianIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
        call = await provider.issue_notification_schemes.add_notifications(arguments)
        result = await call.wait()
        return result.body_json()

Input

Field	Type	Presence	Description and constraints
$	object	Root	Additional keys: not allowed
path	object	Required within parent	Additional keys: not allowed
path.cloudId	string	Required within parent	Pattern: ^[0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{4}-[0-9a-fA-F]{12}$
path.id	string	Required within parent
body	Model	Required within parent	Expand Add notifications to notification scheme — request body — body

Referenced models: Add notifications to notification scheme — request body — body

Response

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

Field	Type	Presence	Description and constraints
$	null	Root

Schemas

Add notifications to notification scheme — request body — body

Field	Type	Presence	Description and constraints
$	object	Root	Details of notifications which should be added to the notification scheme. Additional keys: allowed
notificationSchemeEvents	array	Required within parent	The list of notifications which should be added to the notification scheme. write Only: true
notificationSchemeEvents[]	Model	Each item	Expand Create notification scheme — request body — body notification Scheme Events item

Referenced models: Create notification scheme — request body — body notification Scheme Events item

Create notification scheme — request body — body notification Scheme Events item

Field	Type	Presence	Description and constraints
$	object	Root	Details of a notification scheme event. write Only: true Additional keys: allowed
event	Model	Required within parent	Expand Create notification scheme — request body — body notification Scheme Events item event The ID of the event.
notifications	array	Required within parent	The list of notifications mapped to a specified event. Maximum length: 255 write Only: true
notifications[]	Model	Each item	Expand Create notification scheme — request body — body notification Scheme Events item notifications item

Referenced models: Create notification scheme — request body — body notification Scheme Events item event, Create notification scheme — request body — body notification Scheme Events item notifications item

Create notification scheme — request body — body notification Scheme Events item event

Field	Type	Presence	Description and constraints
$	object	Root	The ID of an event that is being mapped to notifications. write Only: true Additional keys: allowed
id	string	Required within parent	The ID of the notification scheme event. write Only: true

Create notification scheme — request body — body notification Scheme Events item notifications item

Field	Type	Presence	Description and constraints
$	object	Root	Details of a notification within a notification scheme. Maximum length: 255 write Only: true Additional keys: allowed
notificationType	string	Required within parent	The notification type, e.g `CurrentAssignee`, `Group`, `EmailAddress`. write Only: true
parameter	string	Optional	The value corresponding to the specified notification type. write Only: true

Policy, approvals and errors

SDK function policy ID: atlassian.addnotifications. Catalog operation: addNotifications. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["manage:jira-configuration"]

No-content response statuses: [204]

Official provider source