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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,555,948
Community Members
 
Community Events
184
Community Groups

Getting http 400 error on statuspage.io incident post

I'm using node.js to post incidents to our statuspage.io and getting a 400 error.  Based on the API docs, which show Curl examples, I'm formatting the post data as:

var postData = querystring.stringify({

'incident[name]': "Network routing issue",

'incident[status]': "identified",

'incident[body]': "body text...",

'incident[component_ids][]': "bk60bdqdqv7g",

'incident[components][bk60bdqdqv7g]': "degraded_performance"

});

The raw postData result string looks like:

postData="incident%5Bname%5D=Network%20routing%20issue&incident%5Bstatus%5D=identified&incident%5Bbody%5D=This%20is%20a%20test%20message%20body.%20%20Had%20this%20been%20a%20real%20incident%2C%20this%20would%20have%20hopefully%20contained%20some%20useful%20information.&incident%5Bcomponent_ids%5D%5B%5D=bk60bdqdqv7g&incident%5Bcomponents%5D%5Bbk60bdqdqv7g%5D=degraded_performance"

I'm sure that I'm not correctly translating the Curl example to javascript object.

Any pointers, examples, advice would be greatly appreciated.

 

2 answers

1 accepted

0 votes
Answer accepted

I've resolved this issue -- I was not sending the correct Content-Type and Content-Length headers.  With Content-Type set to "application/x-www-form-urlencoded" and Content-Length set to the post data length, I got back the expected 201 (success) status.

After a bit more reading, I've corrected one issue (the component_ids parameter), but still getting the 400 error.

The post data object is:

{

"incident[name]": "Network routing issue",

"incident[status]": "identified",

"incident[body]": "This is a test message body. Had this been a real incident, this would have hopefully contained some useful information.",

"incident[component_ids]": [ "bk60bdqdqv7g" ]

}

The post data string is:

incident%5Bname%5D=Network%20routing%20issue&incident%5Bstatus%5D=identified&incident%5Bbody%5D=This%20is%20a%20test%20message%20body.%20%20Had%20this%20been%20a%20real%20incident%2C%20this%20would%20have%20hopefully%20contained%20some%20useful%20information.&incident%5Bcomponent_ids%5D=bk60bdqdqv7g

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events