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!


Using the API - Separating Prod from Non-Prod

We'd like to primarily do an integration with our products and the Statuspage API.  To do that, we want to have separation between development/testing and production - we don't want to have an API key used in development that could accidentally post to production.

We initially thought we could use two different pages:  a prod page and a non-prod page.  However, we have the following obstacle: There doesn't seem to be an association between an API key and a page.  The API keys have access to all pages associated with our 'organization'.

Two questions:

1) What is the best way to keep this separation?  Can we have two different 'accounts' that are not tied together in any way?  

2) Since we want to use the API but not publish a status page, do we have to activate the pages to use the API?


1 answer

1 accepted

0 votes
Answer accepted

So I only just started experimenting with additional pages. the plan you are on determines how many public pages you can have.  It does appear you can have pages which are not-activated, meaning they are not public.  This is a new space I am looking at so I can't be more specific.

But it looks like you can have more than one API key.  In click on your profile avatar in the bottom left of the sidebar. 

Screen Shot 2021-01-06 at 7.23.17 AM.png

Click on API Info and then click on "Create Key"

Screen Shot 2021-01-06 at 7.23.29 AM.pngSo I think you can accomplish what you are trying to do.  However, I don't think you can prevent one key from only being able to update one page and not be able to update a different page.  But if you are using automation to update your pages, then using a different API Key and Page ID in your automation, you could get close.



Thanks Chris.  Unfortunately, close isn't probably good enough.  I did experiment with using two different email addresses to create two different pages, totally separate from each other.  I then tried to grant one of my users access to the other page, and when I do that, the system mysteriously creates an 'organization' (something that you can't seem to manage, and I don't know how it names the organization, other than using the first word of my page name), and I can jump between the organizations.  That might be the best we can do, but I'd like to remove the mystery from this and understand what it is doing.

Well, I suppose yo could have two different accounts which are not connected.  then you'd up with completely different API key and page IDs.  You also end up with different URLs, which may or may not be manageable.  I don't really know if you can do what you are trying to accomplish unless yo go to a paid plan where you can get some "real" tech support. :-)

Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events