POST/v1/notification/rule/{ruleUuid}/team/{teamUuid}

Adds a team to a notification rule

Requires permission SYSTEM_CONFIGURATION or SYSTEM_CONFIGURATION_UPDATE

  • IdempotentThe SDK sends Idempotency-Key, so a retried request is only applied once.

2 parameters
ruleUuidstringrequired
The UUID of the rule to add a team to
teamUuidstringrequired
The UUID of the team to add to the rule

4 status codes
200The updated notification rule
enabledbooleanoptional
filterExpressionstringoptional
logSuccessfulPublishbooleanoptional
messagestringoptional
namestringrequired
notificationLevelstringoptional
Allowed:INFORMATIONALWARNINGERROR
notifyChildrenbooleanoptional
notifyOnarray<string>optional
projectsarray<object>optional
publisherobjectoptional
publisherConfigstringoptional
scheduleCronstringoptional
Schedule of this rule as cron expression. Must not be set for rules with trigger type EVENT.
scheduleLastTriggeredAtintegeroptional
When the schedule last triggered, as UNIX epoch timestamp in milliseconds
scheduleNextTriggerAtintegeroptional
When the schedule triggers next, as UNIX epoch timestamp in milliseconds
scheduleSkipUnchangedbooleanoptional
Whether to skip emitting a scheduled notification if it doesn't contain any changes since its last emission. Must not be set for rules with trigger type EVENT.
scopestringrequired
Allowed:SYSTEMPORTFOLIO
tagsarray<object>optional
teamsarray<object>optional
triggerTypestringrequired
Allowed:EVENTSCHEDULE
uuidstringrequired
304The rule already has the specified team assigned
401Unauthorized
404The notification rule or team could not be found

Error handling

A 401 is returned: Unauthorized. A 404 is returned: The notification rule or team could not be found.