# Statuspage integrations

> Call the Statuspage API from any Tray.ai workflow with the HTTP Connector.

**Canonical page:** https://tray.ai/connectors/statuspage-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Statuspage is Atlassian's hosted status page service for publishing component status, incidents and scheduled maintenance to customers and notifying subscribers. Tray.ai connects to Statuspage through the HTTP Connector, so your workflows can call the Statuspage API alongside the rest of your stack.

## Use cases

### Incidents

Read, create, update, and delete incidents in Statuspage from any Tray.ai workflow. The Statuspage API covers calls such as list incidents and create an incident.

- List incidents
- Create an incident
- Update an incident

### Components

Read, create, update, and delete components in Statuspage from any Tray.ai workflow. The Statuspage API covers calls such as list components and create a component.

- List components
- Create a component
- Update a component

### Subscribers

Read, create, and update subscribers in Statuspage from any Tray.ai workflow. The Statuspage API covers calls such as list subscribers and create a subscriber.

- List subscribers
- Create a subscriber
- Update a subscriber

### Metrics

Read, create, and delete metrics in Statuspage from any Tray.ai workflow. The Statuspage API covers calls such as list metrics and add metric data points.

- List metrics
- Add metric data points
- Delete a metric

### Pages

Read and update pages in Statuspage from any Tray.ai workflow. The Statuspage API covers calls such as list pages and get a page.

- List pages
- Get a page
- Update a page

### Statuspage events

Start a Tray.ai workflow the moment something happens in Statuspage. Statuspage sends events such as incident created and incident updated to a Tray.ai webhook trigger.

- Incident created
- Incident updated
- Component status changed

## Challenges Tray.ai solves

### Keeping Statuspage credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Statuspage credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Statuspage API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Statuspage API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Statuspage?

Yes. Tray.ai connects to Statuspage through the HTTP Connector, which calls the Statuspage API directly. Any call the Statuspage API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Statuspage?

The Statuspage API uses an API key in a request header and an API key in the query string. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Statuspage connector?

Statuspage runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Statuspage connector from the Statuspage API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/