Appearance
List issues across the current site status pages ​
Tenant/site scoped, including page names and latest updates. Ongoing means unresolved AND unarchived, including legacy issues without archived_at. History means resolved OR archived. Returns items, filters, total, pages, navigation_html and HTML. Twenty issues per page with stable start-time/ID order. Public history continues to include all issues.
Request preparation ​
Send a GET request to /sites/{siteId}/status/issues 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:
siteId(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.month(query, optional): UTC start month, years 2000 to 9998.date(query, optional): UTC start date; must be within month when both are supplied.component(query, optional): Opaque component ID from this page, including historical components.state(query, optional): Use the type and constraints shown in the parameter reference.status_page(query, optional): Optional status page within this site. Omit for all site pages.
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 ​
The specification lists these security alternatives: AdminSession, BearerAuth, AccessToken. Read any operation-specific restrictions as well: browser-session, account-role, and signed-user requirements may impose additional conditions. See authentication before choosing a credential.
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 List issues across the current site status pages are:
- 200: Saved state or server-rendered HTML fragment. No credentials are returned.
- 400: Invalid input
- 403: Account admin or plan access required
- 404: Site or status page unavailable in this account
- 409: Slug, portal page, or hostname collision
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.
List issues across the current site status pages​
GET
/sites/{siteId}/status/issues
Tenant/site scoped, including page names and latest updates. Ongoing means unresolved AND unarchived, including legacy issues without archived_at. History means resolved OR archived. Returns items, filters, total, pages, navigation_html and HTML. Twenty issues per page with stable start-time/ID order. Public history continues to include all issues.
Authorizations​
AdminSession
Authenticated backend-admin session cookie.
Type
API Key (cookie: connect.sid)
or
BearerAuth
JWT token from login
Type
HTTP (bearer)
or
AccessToken
Personal access token. Value: Token <your-token>
Type
API Key (header: Authorization)
Parameters​
Path Parameters
siteId*
Type
Requiredstring
Pattern
"^[a-fA-F0-9]{24}$"Query Parameters
page
20 issues per page, ordered by start time and ID descending.
Type
integer
Minimum
1Maximum
999999Default
1month
UTC start month, years 2000 to 9998.
Type
string
Pattern
"^\\d{4}-\\d{2}$"date
UTC start date; must be within month when both are supplied.
Type
string
Format
"date"component
Opaque component ID from this page, including historical components.
Type
string
Pattern
"^[a-fA-F0-9]{24}$"state
Type
string
Valid values
"ongoing""history""all"Default
"ongoing"status_page
Optional status page within this site. Omit for all site pages.
Type
string
Pattern
"^[a-fA-F0-9]{24}$"Responses​
Saved state or server-rendered HTML fragment. No credentials are returned.