info

About Our Data Source

Our data is not Hazard Hub data. Our data is created by the same people who made the original Hazard Hub models and algorithms. However, there are some significant differences, mostly improvements in delivery and comprehensiveness of the data, focusing in on the key pieces of information customers really use. For example there are new hazard fields and many more ways to better understand the area of the risk. There are a number of other small changes, but accuracy and easy of use and cost-effectiveness are paramount to everything our data provider does.

Switch from HazardHub to PerilPulse

Migration is as simple as changing your base URL. Same endpoints, same response format, better pricing.

🎯 Smart Coverage: We analyzed thousands of API calls and discovered that most users only need a fraction of the available data fields. By focusing on the essential risk assessment data that actually drives underwriting decisions, we can offer you the same insights at significantly lower cost. It's not about having less—it's about having exactly what you need.

How Easy Is Migration?

Your Current Code

api.hazardhub.com/v1/risks

Expensive • Contracts • Minimums

arrow_forward

Just Change URL!

Your New Code

api.perilpulse.com/v1/risks

$1.40/query • No contracts • No minimums

Migration Steps

1

Sign Up for PerilPulse

Create your account and get your API key. Start with just a $50 deposit.

2

Update Your Base URL

Change api.hazardhub.com to api.perilpulse.com

3

Update Your API Key

Replace your HazardHub token with your new PerilPulse API key.

4

That's It! 🎉

Your application now uses PerilPulse. Same data structure, better pricing.

API Response Format

Here's an example of the complete response you'll receive from PerilPulse. The structure matches HazardHub for seamless migration.

The Supreme Court says you can't copyright a JSON schema: Google LLC v. Oracle America, Inc., 593 U.S. 1 (2021)

Complete API Response

Visual Risk Summary

Same complete API response with visual risk indicators added

Field Availability Guide

🟢
Green Fields

These fields are available in PerilPulse and will be populated in your API responses.

🔴
Red Fields

These fields are not available in PerilPulse. They will not appear in API responses.

Code Examples

Before: HazardHub

javascript 
const response = await fetch(
  'https://api.hazardhub.com/v1/risks?' +
  'address=123+Main+St&city=Austin&state=TX',
  {
    headers: {
      'Authorization': 'Token token=YOUR_HAZARDHUB_KEY'
    }
  }
);

After: PerilPulse

javascript 
const response = await fetch(
  'https://api.perilpulse.com/v1/risks?' +
  'address=123+Main+St&city=Austin&state=TX',
  {
    headers: {
      'Authorization': 'Token token=YOUR_PERILPULSE_KEY'
    }
  }
);

info Only two changes needed: base URL and API key

Migration FAQ

help_outline Will I need to change my code?

No code changes required! Just update your base URL and API key. All endpoints and response formats are identical.

help_outline What about my existing integrations?

They'll work exactly as before. PerilPulse is a drop-in replacement, so your existing integrations will continue functioning without modification.

help_outline How long does migration take?

Most customers complete migration in under 5 minutes. It's literally just changing two configuration values.

help_outline Is there any downtime?

Zero downtime! You can test PerilPulse alongside HazardHub, then switch when you're ready.

Ready to Save Money?

Join hundreds of companies who've already made the switch

Start Migration Now View API Docs
Lower
Cost Per Query
<5min
Migration Time
$0
Setup Fees