Webhooks logoIntegrations · Webhooks

Every Matching Lead, Delivered as JSON to Your Endpoint

The integration for teams with their own stack: FirstLeads posts each matching incident to a URL you control, so fire leads flow into your custom CRM, dialer, dashboard, or data warehouse.

Quick Answer

FirstLeads webhooks POST a JSON payload to your endpoint whenever an incident matches your alerts — incident details, address, damage level, and lead identifiers your system can act on. Pair them with the API to pull full property and contact detail. Contact us for the event and payload reference.

Every other integration on this page is a specific instance of the same idea: an incident matches your alert, and the data goes where your team works. Webhooks hand you that primitive directly. Point an alert at an HTTPS endpoint and every matching incident arrives as a JSON POST — ready for your CRM import, your dialer queue, a county dashboard, or whatever your ops team dreams up.

If you are evaluating a custom build, contact us for the event catalog and payload schemas, or see the API documentation for programmatic access to the full lead files.

Getting connected

1

Stand up an endpoint

Any HTTPS URL that accepts a JSON POST works — a serverless function, your backend, or an automation platform endpoint.

2

Point an alert at it

Configure the webhook as a delivery channel on your alerts. Each matching incident POSTs once, with retries on failure.

3

Enrich via the API

Payloads carry lead identifiers — use the FirstLeads API to pull full property detail and unlocked owner contacts into your system. Contact us for the payload reference and support while you build.

Works with

Building on FirstLeads data?

Contact us for the webhook event reference and API docs — our team supports custom builds from first payload to production.

Frequently Asked Questions

Keep exploring

See every connection on the FirstLeads integrations page.