API service

Apply configuration-specific traffic decisions

Blocker V2 evaluates richer request context through a named configuration and returns the exact access and page response fields your integration should follow.

GET /services/blockerv2

View API documentation Create account

How it works

Different rules for different traffic flows

Each request identifies a configuration with confname. In addition to IP, user agent, and URL, an integration can submit JSON params and headers so the selected configuration can evaluate more of the original request.

isBot is the visitor classification, while blockAccess is the final policy decision. Integrations should also follow pageResponseType and pageResponseContents when applying the configured response.

Response fieldsGET /services/blockerv2

isBotBot classification produced by the selected configuration

blockAccessFinal access decision for the current request

pageResponseTypeConfigured action type: RedirectURL, HTTPStatusCode, or None

pageResponseContentsRedirect destination, HTTP status value, or Stay On Page

Integration examples

Evaluate a request with Blocker V2

Submit a named configuration together with visitor context and optional JSON params and headers, then read the flat JSON response.

Replace the configuration placeholder, collect only the request context your rules require, and follow the returned access and page response fields exactly. Read the complete Blocker V2 documentation.

Threat radar identifying suspicious traffic

Core capabilities

What Blocker V2 provides

Named configurations

Create multiple configurations and select the appropriate rules for each site, path, or application flow.

Extended request context

Accepts optional user agent, URL, JSON params, and JSON headers in addition to the visitor IP.

Controlled responses

Returns the configured redirect, HTTP status, or stay-on-page action without hiding the underlying access decision.

WordPress integration

The official Stopbot WordPress plugin applies Blocker V2 decisions to public frontend page requests.

Use cases

Where Blocker V2 fits

Site-area policies

Apply separate configurations to public content, campaigns, account pages, or other protected areas.

Server-side protection

Inspect the original request before the application continues with its normal response.

WordPress websites

Use the official plugin when a WordPress installation needs a guided Blocker V2 integration.

Start using Blocker V2

Create an account, configure the service in the Stopbot panel, and follow the integration documentation for your application.

Create account Compare plans