Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Error 422 Unprocessable Entity creating new Integration Action for CloudWatch integration.


Hi All,


I'm trying to use the Integration API to create a new CloudWatch integration then dynamically add new integration actions to that integration.

The CloudWatch integration gets set up fine. I then take the values for IntegrationId and ApiKey from the new integration and try to add a new action to that integration.
I get error 422 Unprocessable Entity. It doesn't like the format of my json. I've been sure to only include mandatory fields.
Input params are as follows.

$uri = ''
$api = 'GenieKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'
$head = @{"Authorization" = "$api"}
$body = @{"type"="create";"name"="Create Alert -Test";"alias"="alias for this alert"} | ConvertTo-Json
$body = '{\"type\":\"create\",\"name\":\"Create Alert -Test\",\"alias\":\"alias for this alert\"}'

$data = Invoke-RestMethod -Uri $uri -Method Post -Headers $head -ContentType "application/json" -Body $body

The response is:
Invoke-RestMethod : The remote server returned an error: (422) Unprocessable Entity.
At line:1 char:9

Can anyone help me to get the integration to accept this JSON?

Bear in mind, this is a CloudWatch API integration and not the Default API integration.

Any assistance would be greatly appreciated.

1 answer

1 accepted

0 votes
Answer accepted
John M
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Mar 02, 2022 • edited

Hi Joel,

It looks like the following fields are also required for the create action:


"user": "{{user}}",
"note": "{{note}}",
"source": "{{source}}",
"message": "{{message}}",
"description": "{{description}}",
"entity": "{{entity}}"

That doesn't seem to be very clear in the docs; I will put in a request to have them updated. 

Thank you John.
The requests are now getting through.

Like John M likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events