CorefinityCorefinityDocs
Open the Control PanelControl Panel
Error pages · 11 of 12

Test the error pages on the site

Runs a check against the site that changes none of its pages. live asks one of the site's own addresses for a path, as a visitor would, and answers the status, the main headers and who drew the answer; render answers which version of each page the site serves now (while maintenance is on, only the maintenance page). The first render on a site that has never been checked prepares the site instead, which takes a person who may change the site (anyone else is answered 404): the answer then has preparing: true, no pages and the operation_id of the preparation. Follow that id with the general operation endpoint (GET /corestack/operations/{operation}) until its status is completed, then send the request again. The error pages operation endpoint answers changes to the pages only, so it answers 404 for a preparation.

POST/api/corestack/sites/{site}/error-pages/test

Path parameters

siteintegerRequired

The id of a site row. A website's production site and each of its environments has its own id. Digits only. At least 1.

Body

kindstringRequired
liverender
pathstring

For live: the path to ask for, with its query string if any. It starts with a single / and has no spaces, control characters or # fragment. Defaults to /. Up to 512 characters.

Returns

200 The check's result. pages is shortened here.

Fields of the 200 answer

If it is refused

StatusReasonWhat to do
401noneSend a valid token as Authorization: Bearer <token>.
403company_unavailableYour company is unavailable.
403scope_requiredUse a token with the scope named in scope.
403two_factor_requiredTurn on two-factor on your account, then send again.
404feature_offThis feature is not on for your organisation yet.
409managed_elsewhereThis site is read-only here. Change it in the control panel that manages it.
409operation_in_progressA change to the environment is in progress. Try again when it has finished.
409restore_runningA restore is running on the site. Wait for it to finish, then try again.
422invalidFix the field named in field; errors says why.
429rate_limitedWait for the seconds in Retry-After.

Reasons are listed by name in Errors and refusals.

The same task elsewhere

curl -X POST https://manage.corefinity.com/api/corestack/sites/1042/error-pages/test \
  -H "Authorization: Bearer $COREFINITY_TOKEN" \
  -H "Accept: application/json" \
  -H "Content-Type: application/json" \
  -d '{
    "kind": "live",
    "path": "/"
  }'
{
  "body_head": "<!doctype html><html lang=\"en\"><head><title>Harbour & Finch</title>",
  "bytes": 5120,
  "checked_at": "2026-11-06T09:16:40Z",
  "error": null,
  "headers": {
    "cache-control": null,
    "cf-cache-status": null,
    "content-type": "text/html; charset=UTF-8",
    "retry-after": null,
    "server": "nginx"
  },
  "kind": "live",
  "message": null,
  "refused": null,
  "status": 200,
  "truncated": true,
  "url": "https://harbourandfinch.example.com/",
  "who": "app"
}
Try it
Held in this tab's memory only. Never stored or sent to us.

This sends a real POST request and changes your account.

Use a token with only the read scope. How to make one

Was this helpful?
Open in ClaudeOpen in ChatGPT