Skip to content

Read a status page and bounded recent transitions ​

Only enabled pages on active public sites are available. Subscription endpoints are rate limited to ten requests per ten minutes per IP. Subscribe returns pending/confirmed state and a message, never a token or saved preferences. Existing email requests never overwrite preferences. Manage sends an email link and does not delete or disclose tokens; requests for a subscriber are atomically limited to one every ten minutes. Pending confirmation resends use the same cooldown. Confirmed signed links stay stable across requests, are scoped to page and subscription ID, and cease working after deletion. GET links only render the verification/preferences page; confirmation, saving and unsubscribe require explicit POST actions. Browser email storage only prefills this page; verified link capabilities are retained separately for this page in browser storage. Confirm and unsubscribe accept an empty body. Save requires confirmed email and component preferences. Keys, ping URLs, and raw source descriptions are never public.

Request preparation ​

Send a GET request to /status/{slug}/{pageSlug} on the appropriate server. Check the API overview for base URL guidance and the server information in the interactive reference. Replace path placeholders with identifiers from the intended account or site; a similarly named record in another workspace is not interchangeable.

The declared request parameters are:

  • slug (path, required): Use the type and constraints shown in the parameter reference.
  • pageSlug (path, required): Use the type and constraints shown in the parameter reference.
  • page (query, optional): 20 issues per page, ordered by start time and ID descending.

No request body is declared in the current specification. Check the route and any documented parameters before sending the request rather than adding an arbitrary JSON payload.

Authentication and scope ​

This operation does not declare an OpenAPI security requirement. Check the description and parameter definitions for any signed URL, customer identity, webhook, or browser-session conditions before using it outside a test environment.

Keep credentials in the appropriate private configuration and remove secrets from shared logs. Confirm the target resource belongs to the intended workflow before issuing a request. Authentication alone should not be treated as confirmation that a supplied account, site, or customer identifier is correct.

Response handling ​

The documented responses for Read a status page and bounded recent transitions are:

  • 200: HTML page or subscription acknowledgement
  • 400: Invalid preferences or expired confirmation link
  • 404: Disabled, unavailable, or incorrect page or token
  • 429: Too many subscription requests

Begin with a known record or a narrow query and inspect the returned fields before displaying them to users. Where the operation defines pagination, follow those parameters to retrieve additional results. An empty successful response is different from a failed request; keep errors visible to the calling workflow instead of presenting them as an empty data set.

If a connection fails after submission, investigate the current server state before repeating an action whose outcome is uncertain. When requesting support, retain the method, route, response status, and sanitized error message. The interactive reference below provides the detailed schemas and examples for this specific operation.

Read a status page and bounded recent transitions​

GET
/status/{slug}/{pageSlug}

Only enabled pages on active public sites are available. Subscription endpoints are rate limited to ten requests per ten minutes per IP. Subscribe returns pending/confirmed state and a message, never a token or saved preferences. Existing email requests never overwrite preferences. Manage sends an email link and does not delete or disclose tokens; requests for a subscriber are atomically limited to one every ten minutes. Pending confirmation resends use the same cooldown. Confirmed signed links stay stable across requests, are scoped to page and subscription ID, and cease working after deletion. GET links only render the verification/preferences page; confirmation, saving and unsubscribe require explicit POST actions. Browser email storage only prefills this page; verified link capabilities are retained separately for this page in browser storage. Confirm and unsubscribe accept an empty body. Save requires confirmed email and component preferences. Keys, ping URLs, and raw source descriptions are never public.

Parameters​

Path Parameters

slug*
Type
string
Required
pageSlug*
Type
string
Required

Query Parameters

page

20 issues per page, ordered by start time and ID descending.

Type
integer
Minimum
1
Maximum
999999
Default
1

Responses​

HTML page or subscription acknowledgement

Playground​

Variables
Key
Value

Samples​

Powered by VitePress OpenAPI