Help4 Net

JSON-first Cache Refresh for Help4 CDN

Use this flow for W3 Total Cache and custom integrations. Send authenticated JSON POST requests instead of direct PHP bridge calls.

Migration notice: direct PHP bridge compatibility is still available today, but it may not stay long-term. New integrations should move to JSON POST now.

Authentication

Preferred

X-Help4-Api-Key + X-Help4-Api-Secret

Legacy

Authorization: Bearer <token>

Where to get key and secret

  1. Sign in to the Help4 Network client portal and confirm the production domain on the active CDN service.
  2. Install the Help4 CDN plugin and complete its first licensing sync.
  3. Reply to the authenticated service onboarding ticket to request or rotate the per-site API pair.
  4. Enter the issued values in the Help4 CDN plugin settings. Do not place the secret in email, chat, a public page, or source control.

For the full domain, plugin, credential, and deployment workflow, read the Enterprise CDN setup guide.

WordPress-local Endpoint

Endpoint: POST /wp-json/help4-cdn/v1/cache/refresh

curl -sS -X POST "https://example.com/wp-json/help4-cdn/v1/cache/refresh" \
  -H "Content-Type: application/json" \
  -H "X-Help4-Api-Key: YOUR_HELP4_KEY" \
  -H "X-Help4-Api-Secret: YOUR_HELP4_SECRET" \
  -d '{
    "scope": "paths",
    "paths": ["/", "/wp-content/uploads/logo.png"],
    "reason": "deploy",
    "source": "w3tc-webhook"
  }'

Domain-wide clear:

{
  "scope": "domain",
  "clearAll": true,
  "reason": "theme-update",
  "source": "custom-deploy"
}

Control-plane Endpoint

Endpoint: POST /v1/sites/{siteId}/purge

curl -sS -X POST "https://control.help4.net/v1/sites/site_abc123/purge" \
  -H "Content-Type: application/json" \
  -H "X-Help4-Api-Key: YOUR_HELP4_KEY" \
  -H "X-Help4-Api-Secret: YOUR_HELP4_SECRET" \
  -d '{
    "scope": "paths",
    "paths": ["/blog/"],
    "reason": "content-update",
    "requestContext": { "source": "w3tc-integration" }
  }'