Statuspage API

Name: Statuspage API
Brand: Statuspage API
Availability: InStock

✓ Official Vendor SpecCRMContact ManagementapiKey112 EndpointsREST

For Agents

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

Install Jentic One Beta

Connect the Statuspage API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Statuspage API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Statuspage API.

Get a list of pages

Update a page

Add a page access user

Query and filter Statuspage API records by parameters

GET STARTED

Start building with Statuspage API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Statuspage API for, with concrete tasks.

★ 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.

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.

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.

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

Key Endpoints

112 endpoints — code of conduct please don't abuse the api, and please report all feature requests and issues to https://support.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using Statuspage API through Jentic.

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.

Statuspage API

Connect the Statuspage API to your agent

Capabilities

Start building with Statuspage API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs