canonical: https://jentic.com/apis/statuspage.io/statuspage

# Statuspage API

Code of Conduct Please don't abuse the API, and please report all feature requests and issues to https://support.atlassian.com/contact Rate Limiting Each API token is limited to 1 request / second as measured on a 60 second rolling window. To get this limit increased, please contact us at https://support.atlassian.com/contact Error codes 420 or 429 indicate that you have exceeded the rate limit an. The API exposes 112 endpoints secured with apiKey authentication.

## For AI agents

Programmatically get a list of pages, get a page. Covers 112 operations with apiKey authentication.

## Scope

Does not handle payments, communications, or developer tools - use for crm only.

## Capabilities

- Get a list of pages
- Update a page
- Add a page access user
- Query and filter Statuspage API records by parameters
- Monitor Statuspage API operational status and events

## Use cases

### CRM Operations

Use the Statuspage API to perform crm operations programmatically. The API provides 112 endpoints covering core functionality including get a list of pages, get a page, update a page.

Example prompt: Call GET /pages to get a list of pages

### Automated permissions Management

Automate permissions operations by combining multiple Statuspage API endpoints. Agents can get a page and then update a page in a single workflow.

Example prompt: Call GET /pages/{page_id} to get a page, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Statuspage API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Example prompt: Search Jentic for 'get a list of pages', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /pages | Get a list of pages |
| GET | /pages/{page_id} | Get a page |
| PUT | /pages/{page_id} | Update a page |
| PATCH | /pages/{page_id} | Update a page |
| POST | /pages/{page_id}/page_access_users | Add a page access user |
| GET | /pages/{page_id}/page_access_users | Get a list of page access users |
| GET | /pages/{page_id}/page_access_users/{page_access_user_id} | Get page access user |
| PUT | /pages/{page_id}/page_access_users/{page_access_user_id} | Update page access user |

## Key resources

- **permissions** — Operations about permissions
- **status embed config** — Operations about status embed configs.
- **pages** — Your page profile drives basic settings for your status page including your company name,
notificati
- **page access users** — Page access users allow you to limit people who can see your status page via a login. It
also allows
- **page access user components** — Operations related to page access user components

## Why Jentic

- **Setup:** Wiring the Statuspage API by hand means setting up its Authorization header key, working through more than a hundred endpoints, and threading the page id through page-access, component and incident calls yourself. Through Jentic you install once, import the Statuspage API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** Statuspage puts the page id in the URL path (/pages/{page_id}/...), so a rule can pin your agent to one page: it can read and manage that page's access users and nothing else. You choose the operations it may call, so page updates are not included unless you add them.
- **Credential handling:** Your Statuspage API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list pages' or 'add a page access user', and Jentic returns the matching Statuspage API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Statuspage API use?

The Statuspage API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context.

### Can I get a list of pages with the Statuspage API?

Yes. Use the GET /pages endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Statuspage API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

### How do I get a list of pages through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get a list of pages'. Jentic returns the matching Statuspage API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Statuspage API have?

The Statuspage API exposes 112 endpoints covering permissions, status embed config, pages operations.

### Can I limit what my agent is allowed to do with the Statuspage API?

Yes. Jentic One is self-hosted, so your own rules decide which Statuspage operations and credentials the agent may use. Because Statuspage puts the page id in the URL path (/pages/{page_id}/...), you can pin the agent to a single page and let it only read and manage that page's access users through the page_access_users endpoints. Page updates such as PUT /pages/{page_id} stay off limits unless you explicitly add them to the allowed operations.