Skip to content

Archive an issue without resolving it or notifying subscribers ​

Site/account/page scoped. Owner/admin access is required for editor and mutations. Uses the status site mutation guard. Mutations return issue, id, page, revision and server-rendered item HTML. Reconcile the filtered list through its GET endpoint for current pagination. Creation also returns editor_html from the write result. Use the page query parameter on the list endpoint to preserve the current admin list page. Request IDs make create/append retries idempotent. Stale revisions and the explicit 1000-update limit return 409. History corrections preserve timestamps and use revision protection. Identical edits and deleted-update retries are idempotent. At least one update must remain. Status, resolved_at and started_at derive from remaining updates. Corrections suppress pending outbox and delivery content for that update and send no new emails; sent emails cannot be recalled. Resolving retains history. Creating and appending queue opted-in subscriber emails; metadata edits and archives send none. Archiving sets archived_at without changing status, resolved_at or updates. Retries of an already archived issue are idempotent, even with the original revision. A stale revision on an unarchived issue returns 409. Archived issues leave ongoing and public active lists but retain public history and detail. There is no restore action. Deleting the page/site/account removes issues.

Request preparation ​

Send a POST request to /sites/{siteId}/status/pages/{id}/issues/{issueId}/archive 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.
  • id (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.

This operation defines a required request body. Documented media types: application/json. Review required fields, nested objects, and allowed values in the request schema. Keep identifiers and field types intact when replacing example data with your own values.

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 Archive an issue without resolving it or notifying subscribers 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

Exercise this operation with controlled test data before enabling it in an automated workflow. Validate the request against the schema and inspect the response before updating local state. Do not assume that a successful response means background processing has finished; follow any documented status or follow-up operation when the action queues additional work.

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.

Archive an issue without resolving it or notifying subscribers​

POST
/sites/{siteId}/status/pages/{id}/issues/{issueId}/archive

Site/account/page scoped. Owner/admin access is required for editor and mutations. Uses the status site mutation guard. Mutations return issue, id, page, revision and server-rendered item HTML. Reconcile the filtered list through its GET endpoint for current pagination. Creation also returns editor_html from the write result. Use the page query parameter on the list endpoint to preserve the current admin list page. Request IDs make create/append retries idempotent. Stale revisions and the explicit 1000-update limit return 409. History corrections preserve timestamps and use revision protection. Identical edits and deleted-update retries are idempotent. At least one update must remain. Status, resolved_at and started_at derive from remaining updates. Corrections suppress pending outbox and delivery content for that update and send no new emails; sent emails cannot be recalled. Resolving retains history. Creating and appending queue opted-in subscriber emails; metadata edits and archives send none. Archiving sets archived_at without changing status, resolved_at or updates. Retries of an already archived issue are idempotent, even with the original revision. A stale revision on an unarchived issue returns 409. Archived issues leave ongoing and public active lists but retain public history and detail. There is no restore action. Deleting the page/site/account removes 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
string
Required
Pattern
"^[a-fA-F0-9]{24}$"
id*
Type
string
Required
issueId*
Type
string
Required
Pattern
"^[a-fA-F0-9]{24}$"

Request Body​

application/json
JSON
{
  
"revision": 0
}

Responses​

Saved state or server-rendered HTML fragment. No credentials are returned.

Playground​

Authorization
Variables
Key
Value
Body

Samples​

Powered by VitePress OpenAPI