nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Which statuspage api should we use? v1 or v2?

Nikita Nemykin

Status page docs offers endpoints which can be used only with API key. We also found a library which uses v2 endpoints. But it's mentioned here that v2 endpoints are deprecated. Also I haven't managed to find any docs about v2 endpoints.

For us it's more convenient to use v2 api since it doesn't require api key and doesn't have as strict limit restrictions as v1 api has. In addition to that v2 also seems more preferable because it's easier to make requests without need to proxy them like it seems necessary to do for v1 api.

Are permissions calls to v2 api limited to GET only requests? Are there any docs on v2 api? Is v2 api deprecated?

Accepted answers

Zeeshan_twdimt

Hey @Nikita Nemykin

We have two APIs:

Manage API: The authenticated API found at https://developer.statuspage.io/ for managing the page - this is the v1 API you are referring to.
Page API: An unauthenticated Status API for querying information from the page and embedding it elsewhere. The Status API can be found at your status page domain appending with '/api' - for example, https://status.newrelic.com/api - these contain the v2 endpoints.

You can find more information on that here: https://support.atlassian.com/statuspage/docs/what-are-the-different-apis-under-statuspage/

All comments

Zeeshan_twdimt

Hey @Nikita Nemykin

We have two APIs:

Manage API: The authenticated API found at https://developer.statuspage.io/ for managing the page - this is the v1 API you are referring to.
Page API: An unauthenticated Status API for querying information from the page and embedding it elsewhere. The Status API can be found at your status page domain appending with '/api' - for example, https://status.newrelic.com/api - these contain the v2 endpoints.

You can find more information on that here: https://support.atlassian.com/statuspage/docs/what-are-the-different-apis-under-statuspage/

Nikita Nemykin

How risky is it to use Page API because your colleague said that it's deprecated? https://community.atlassian.com/t5/Statuspage-questions/StatusPage-io-v2-api-subscribers-endpoint-not-returning-all/qaq-p/944674

Zeeshan_twdimt

My colleague there means that the endpoints like ‘api.statuspage.io/v2/<endpoints>’ were deprecated.

The Page API uses something like ’status.twilio.com/api/v2/<endpoints>', which is different than what was deprecated and is working as expected.

Raghav, Praveen

Hi @Zeeshan ,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

rest-api

statuspage