Appearance
Read issue overview, manual impact timeline and complete update history ​
HTML on active public pages/sites only. Portal and standalone custom domains preserve branding and navigation. Issue components use opaque page IDs and name snapshots. Manual impact intervals are separate from measured Beatmonks uptime. Archive lists use 20-item pagination and UTC dates. No source keys, API keys or ping URLs are exposed.
Request preparation ​
Send a GET request to /s/{slug}/status/issues/{issueId} 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.issueId(path, required): Use the type and constraints shown in the parameter reference.
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 issue overview, manual impact timeline and complete update history 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 issue overview, manual impact timeline and complete update history​
GET
/s/{slug}/status/issues/{issueId}
HTML on active public pages/sites only. Portal and standalone custom domains preserve branding and navigation. Issue components use opaque page IDs and name snapshots. Manual impact intervals are separate from measured Beatmonks uptime. Archive lists use 20-item pagination and UTC dates. No source keys, API keys or ping URLs are exposed.
Parameters​
Path Parameters
slug*
Type
Requiredstring
issueId*
Type
Requiredstring
Pattern
"^[a-fA-F0-9]{24}$"Responses​
HTML page or subscription acknowledgement