Skip to main content
POST
/
status-page
/
create
Create status page
curl --request POST \
  --url 'https://api.flashcat.cloud/status-page/create?app_key=' \
  --header 'Content-Type: application/json' \
  --data '
{
  "name": "My Status Page",
  "url_name": "my-status-page",
  "type": "public",
  "page_header": "Welcome to our status page",
  "contact_info": "mailto:support@example.com"
}
'
{
  "request_id": "01HK8XQE3Z7JM2NTFQ5YJ8P9R4",
  "data": {
    "page_id": 6294565612043,
    "page_name": "My Status Page",
    "page_url_name": "my-status-page"
  }
}

​
Restrictions

AspectValue
Rate limits1,000 requests/minute; 50 requests/second per account
PermissionsStatus Pages Manage (on-call)

Authorizations

​
app_key
string
query
required

App key issued from the Flashduty console under Account → APP Keys. Required on every public API call. Keep it secret — it grants the same access as the owning account.

Body

application/json
​
name
string
required

Display name of the status page.

Maximum string length: 255
​
url_name
string
required

URL-safe slug, unique per account and page type.

Maximum string length: 255
​
type
enum<string>
required

Visibility type of the status page.

Available options:
public,
internal
​
date_view
enum<string>
required

How event dates are displayed.

Available options:
calendar,
list
​
display_uptime_mode
enum<string>
required

How uptime is displayed.

Available options:
chart_and_percentage,
chart,
none
​
custom_domain
string

Custom domain for a public status page.

Maximum string length: 255
​
page_title
string

Browser title shown for the status page.

​
page_header
string

Header content shown on the status page.

​
page_footer
string

Footer content shown on the status page.

​
custom_links
object[]

Custom navigation links shown on the status page.

​
contact_info
string

Get-in-touch contact, such as a mailto or website URL.

​
subscription
object

Response

Success

Success response envelope. On every 2xx response, request_id identifies the call (also mirrored in the Flashcat-Request-Id header) and data holds the endpoint-specific payload. Failure responses use a different shape — see ErrorResponse.

​
request_id
string
required

Unique ID for this request. Mirrored in the Flashcat-Request-Id response header. Include it when reporting issues.

Example:

"01HK8XQE3Z7JM2NTFQ5YJ8P9R4"

​
data
object
required

Endpoint-specific payload. See each operation's 200 response schema.