SafeWeb API

SafeWeb API Documentation

Overview

The SafeWeb Partner API allows you to programmatically manage customers on the SafeWeb dark web monitoring platform. Through the API you can onboard and offboard customers, manage their monitored assets, retrieve breach data and breach categories, and access account-level analytics.

Quick Start

  1. Get your credentials — contact SafeWeb to receive your Partner ID and API key
  2. Test in staging — use the staging environment to onboard a test customer
  3. Verify — confirm the customer is created and monitoring has started
  4. Go live — switch to the production base URL

Authentication

All requests require two headers:

HeaderDescription
SW-PARTNER-IDYour unique partner identifier
SW-API-KEYYour secret API key
curl -X POST https://connect.safeweb.co/api/integrations/customer/onboard \
  -H "Content-Type: application/json" \
  -H "SW-PARTNER-ID: your-partner-id" \
  -H "SW-API-KEY: your-api-key" \
  -d '{ ... }'

Environments

EnvironmentBase URL
Staginghttps://staging-connect.safeweb.co
Productionhttps://connect.safeweb.co

Use the staging environment for development and testing. Both environments behave identically.

API Reference

Customer Lifecycle

Customer Management

Breach Categories

Analytics

Webhooks

Core Concepts

Customers

A customer represents an end user being monitored. Each customer record includes:

  • Contact details — name and email address
  • Monitored assets — one or more domains, email addresses, or both
  • Plan — determines features and monitoring level
  • Billing configuration — currency, billing date, and pricing tier

Once onboarded, SafeWeb handles email discovery, breach scanning, alerts, and reporting automatically.

Plans

PlanDescription
safeweb-basicDark web monitoring with breach alerts
safeweb-plusEverything in Basic, plus a customer self-service portal and monthly security reports

Monitored Assets

SafeWeb monitors two types of assets per customer:

  • Domains — associated email addresses are discovered automatically and monitored for breaches
  • Email addresses — monitored directly against breach databases

At least one domain or email address must be provided when onboarding a customer. Monitoring runs on a daily schedule and requires no further API interaction once configured.

On this page