Re-check a hostname

Asks RedirHub to re-run its checks for the hostname — useful straight after a DNS change instead of waiting for the next scheduled pass.

Base URL: https://api.redirhub.com/v1
Auth: Bearer token
Idempotent: No
Returns: application/json

The request

Call POST /host/{host}/refresh with your bearer token. The host path segment identifies the record.

# Re-check a hostname
curl -X POST "https://api.redirhub.com/v1/host/go.acme.com/refresh" \
  -H "Authorization: Bearer $REDIRHUB_TOKEN"

Path parameters

Parameter	Description
hostRequiredstring

The response

A 200 returns the record as JSON.

{
  "host": "go.acme.com",
  "domain": "string",
  "correct": true,
  "default_require": "ip",
  "require": [
    "string"
  ],
  "current": [
    {
      "type": "link",
      "value": "string",
      "line": "string"
    }
  ],
  "errors": [
    {
      "scope": "string",
      "message": "The given data was invalid.",
      "updated_at": "2026-08-01T09:14:22Z"
    }
  ],
  "counts": [
    "string"
  ],
  "https_requested": true,
  "short_links_enabled": true,
  "public": true,
  "notice": "string",
  "checked_at": "string",
  "created_at": "2026-08-01T09:14:22Z",
  "updated_at": "2026-08-01T09:14:22Z"
}

Status codes

200

SuccessThe hostname after a DNS re-check. Checks are rate limited, so the state may still be the previous one.

401

UnauthenticatedUnauthenticated

429

Too many requestsToo many requests

What usually comes next

One call is rarely the whole job. These are the endpoints most integrations reach for around this one.

Before thisGET /host/{host}What usually comes nextGET /host