Skip to content

Vercel Integration

The WebDecoy Vercel integration automatically blocks malicious IPs at the edge using Vercel’s Firewall API. When a detection occurs, WebDecoy can instantly add the IP to your Vercel project’s firewall deny list.

Detection Created
WebDecoy Rule Engine
├─ Check integration rules
│ ├─ Event type matches?
│ ├─ Bot score threshold met?
│ └─ Decoy filter matches?
Vercel Firewall API
└─ Add IP to deny list

When a detection triggers the integration, WebDecoy calls the Vercel Firewall API (/v1/security/firewall/config) to add the IP address to your project’s deny list.

  • Vercel account (Pro or Enterprise tier for Firewall access)
  • Vercel API token with appropriate permissions
  • A project deployed on Vercel
  1. Go to vercel.com/account/tokens
  2. Click Create Token
  3. Give it a name like “WebDecoy Integration”
  4. Set the scope:
    • For personal accounts: Full Account
    • For team accounts: Select the team
  5. Copy the token (you won’t see it again)
  1. Go to Integrations in the WebDecoy sidebar
  2. Click Vercel
  3. Click Add Vercel Integration
  4. Fill in the configuration:
FieldDescription
NameA friendly name for this integration
API TokenYour Vercel API token
Team IDFor team accounts, enter your team ID (optional for personal accounts)
Project IDScope to a specific project, or leave empty for all projects
ActionWhat to do when triggered (see below)
  1. Click Create Integration

For team accounts:

  1. Go to your Vercel dashboard
  2. Click on your team name
  3. Go to SettingsGeneral
  4. Copy the Team ID (starts with team_)
  1. Go to your project in Vercel
  2. Click SettingsGeneral
  3. Copy the Project ID (starts with prj_)
ActionDescription
Block IPAdd the IP to Vercel’s firewall deny list (403 response)
ChallengeLog only (challenge not supported by Vercel Firewall)
Log OnlyRecord the event without blocking

Choose when the integration should trigger:

OptionDescription
All DetectionsTrigger on any detection
High Risk OnlyOnly trigger when bot score >= 80

Set a threshold score (0-100). The integration only triggers for detections with a bot score at or above this value.

Recommended thresholds:

Use CaseThreshold
Aggressive blocking50+
Standard protection70+
Conservative (fewer false positives)85+

Optionally restrict the integration to specific decoys. Leave empty to trigger for all decoys in your organization.

Each integration shows:

  • Trigger Count - How many times it has fired
  • Failure Count - How many API calls failed
  • Last Triggered - When it last fired
  • Last Error - Most recent error message (if any)

Click Test to verify the integration is working. This sends a test request to the Vercel API.

Toggle integrations on or off without deleting them. Disabled integrations don’t process any detections.

Remove an integration entirely. This doesn’t remove any IPs already blocked in Vercel.

  • Start with “High Risk Only” to avoid false positives
  • Use a conservative bot score threshold initially (75+)
  • Scope to specific projects if you don’t need organization-wide blocking
  • Monitor the failure count for API issues
  • Test the integration after setup
  • Don’t use a personal access token for team projects
  • Don’t set the threshold too low (causes false positives)
  • Don’t ignore failure counts (may indicate permission issues)
  1. Verify your API token is correct
  2. Check the token hasn’t expired
  3. For team accounts, ensure the Team ID is set
  4. Verify the token has permission to modify firewall rules
  1. Verify the Project ID is correct
  2. Ensure the API token has access to the project
  3. For team projects, ensure the Team ID is also set
  1. Check the integration is active (not disabled)
  2. Verify the event type filters match your detections
  3. Check the bot score threshold isn’t too high
  4. Look for errors in the integration status
  1. Check the Last Error message
  2. Verify API token hasn’t been revoked
  3. Ensure you’re on a Vercel plan that includes Firewall access
  4. Check Vercel’s status page for outages

Be aware of Vercel’s limits:

LimitValue
IP rules per projectVaries by plan
API rate limits100 requests/minute

WebDecoy respects these limits and will report errors if limits are exceeded.

To see IPs blocked by WebDecoy:

  1. Go to your Vercel project
  2. Click SettingsSecurityFirewall
  3. View the IP deny list
  4. WebDecoy blocks include a note: “Blocked by WebDecoy - Detection [ID]“

WebDecoy doesn’t automatically remove blocked IPs. To unblock:

  1. Go to your Vercel Firewall settings
  2. Find the IP in the deny list
  3. Remove it manually