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 your Help4 account portal.
  2. Open your active CDN/WAF service.
  3. Open API Access.
  4. Copy your Help4 API Key and Help4 API Secret.
  5. Save both into the Help4 CDN plugin settings.

Managed corporate installs

Some domains are pre-provisioned by Help4 operations with service-level key/secret pairs. Those values are delivered through private ops docs, not public pages.

badpd.com
service_id: 122
profile: prof-ns
migrationmonkey.com
service_id: 123
profile: cartoon-ns
akvapenews.com
service_id: 124
profile: prof-ns
help4wordpress.com
service_id: 125
profile: cartoon-ns

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" }
  }'