Skip to main content

Wordfence Integration

Tier: Basic — Plugin-based toggle integration. Keeps Wordfence's REST namespace available when SyteOps' REST API Restriction is on.

The Wordfence integration in SyteOps is a compatibility toggle. When you enable REST API Restriction, it blocks anonymous REST traffic by default. Wordfence uses its own REST namespace for authentication, configuration, and security operations that need to remain reachable — this toggle ensures that.

What the toggle does​

  • Adds the Wordfence REST namespace to the allowlist when REST API Restriction is enabled.
  • Lets Wordfence continue to receive its own security-related requests without being blocked by SyteOps' restriction.
  • Has no effect when REST API Restriction is off — Wordfence works either way, the toggle just preserves Wordfence's access when everything else is locked down.

Setup​

  1. Install and activate the Wordfence plugin from WordPress → Plugins.
  2. Navigate to SyteOps → Integrations.
  3. Find Wordfence in the Security category.
  4. Toggle it ON and click Save Changes.

If Wordfence isn't installed, SyteOps disables the toggle and shows "Not Installed".

What endpoints become reachable​

When this toggle is on and REST API Restriction is enabled, Wordfence's entire v1 REST namespace is allowed through:

PathPurpose
/wp-json/wordfence/v1/*Wordfence authentication, configuration, and security endpoints

Wordfence verifies its own requests against these endpoints — SyteOps isn't weakening Wordfence's security, just keeping Wordfence's namespace open while everything else stays restricted.

Common use-cases​

  • Sites running both Wordfence and SyteOps REST API Restriction.
  • Security-heavy configurations where you want the REST API locked down but Wordfence's paid features (like Country Blocking or Real-Time IP List) still functioning.