The challenges engineering teams face

  • —User-uploaded files — PDFs submitted through your app need to be screened before they're stored, shared, or processed
  • —User-submitted URLs — Marketplace links, profile URLs, and form inputs that could point to phishing or malware
  • —Signup abuse — Bots and abusers using disposable emails to bypass account restrictions
  • —Alert fatigue — Security events that don't integrate with existing tooling get ignored
  • —Build vs. buy — Building URL, email, and document threat detection from scratch is a multi-month project

How Verifence helps

Drop-in scanning via REST API

Verifence's API is a straightforward REST API authenticated with API keys. Add scanning to any backend service in a day — no complex SDKs, no proprietary formats. Send a file, get a verdict. Send URLs, get verdicts. All responses are structured JSON.

HTTP
POST /api/scan/document
API-KEY: your_api_key
Content-Type: multipart/form-data

file=@upload.pdf

File upload pipeline integration

Add a document scan step to your file ingestion pipeline. When a user uploads a PDF:

  1. 1Accept the file upload
  2. 2POST to Verifence's document scan endpoint
  3. 3If verdict is clean, store and process normally
  4. 4If verdict is threat, reject with an informative error or quarantine for review

Email validation at signup

During user registration, POST the submitted email to Verifence's email scan endpoint before creating the account. Disposable and role addresses return a Block verdict — reject the signup with a clear message. This runs in milliseconds and requires no additional infrastructure.

URL validation for user-submitted content

If users submit URLs (profiles, listings, comments, bios), run them through Verifence's URL scanner before they go live. POST each URL to /api/scan/url and get an immediate Safe or Bad verdict to decide whether to publish or reject.

Event-driven workflows with webhooks

Use webhooks to drive downstream actions from scan events:

document.scanned Block file storage if threat detected
email.scanned Reject signup or flag account for review
brand.impersonation Trigger PagerDuty or Slack alert
url.scanned Auto-reject or quarantine flagged listings

Multiple API keys for environment isolation

Generate separate API keys for dev, staging, and production environments. Revoke keys independently without disrupting other environments.

Integration checklist

  • Generate an API key from Settings → API Keys
  • Add scanning to your file upload handler
  • Add email validation to your registration flow
  • Add URL validation to your content submission handler
  • Configure webhooks for alert routing
  • Set up Brand Monitor for your product domain