Visitor context
Returns IP, hostname, ASN, network type, company, ISP, location, anycast, and detected device information.
API service
Decide which visitors can access your site
Blocker evaluates visitor context against your Stopbot rules and returns both a bot classification and the final access decision for your integration.
GET /services/blockerHow it works
One response for detection and access control
Blocker combines IP and network context, user-agent analysis, URL threat checks, and your configured rules. The response gives your application the information it needs to continue, restrict, or investigate a request.
isBot and blockAccess answer different questions. A visitor can be classified as a non-bot while still being blocked by another configured rule.Response fields
GET /services/blockerisBotBot classification returned by the detection processblockAccessFinal access decision based on the active rulesthreatURLSignal showing whether the submitted URL is considered a threatdetectActivityHuman-readable reason behind the decisionIntegration examples
Call Blocker from your stack
Send visitor IP, user agent, and URL context, then inspect the HTTP status and JSON decision returned by Stopbot.
Replace the example values with the current visitor context, keep the API key in an environment variable, and validate the response before acting on its fields. Read the complete Blocker documentation.
Core capabilities
What Blocker provides
Decision fields
Separates bot classification, access policy, URL threat status, and the reason that produced the result.
Panel controls
Works with the Blocker configuration and the blacklist and whitelist controls managed from the Stopbot panel.
Request logging
Checked frontend visits can be reviewed in Stopbot visitor statistics for operational analysis.
Use cases
Where Blocker fits
Frontend access gate
Evaluate a visitor before rendering a protected page or starting a sensitive workflow.
Traffic screening
Reduce unwanted traffic before it reaches expensive application or advertising flows.
Decision analysis
Use the returned reason and visitor context to understand why traffic was accepted or blocked.
Start using Blocker
Create an account, configure the service in the Stopbot panel, and follow the integration documentation for your application.