Is the Custom API self-serve?

No — it is set up through a conversation with the Partner Success team, who design the feed around your geography, filters, and pull frequency. Head to the Partner Success page to schedule a meeting.

Can the API be limited to certain damage levels or confirmed fires?

Yes. Incident scope is fully tunable: every incident in your territory, confirmed fires only, or a minimum damage threshold such as Medium and High only.

How often can my systems pull data?

Whatever cadence fits your architecture — near real-time polling, hourly batches, or a daily sync. Pull frequency is one of the main things scoped during setup.

What if I just need FirstLeads data in my CRM?

If your goal is leads flowing into a CRM or spreadsheet rather than a raw data feed, the Zapier and HubSpot integrations usually get you there without any custom development.

Features · Custom API

Need Data at Scale? The FirstLeads Custom API

Some businesses don’t need a dashboard — they need a data feed. Pull incident data programmatically into your own tooling, CRM, or pipeline, at whatever volume your territory demands.

Get Started Book a Demo

Quick Answer

The FirstLeads Custom API is a tailored data feed built around your business: scoped to your states, counties, cities, or ZIP codes; filtered to the incidents you care about (confirmed fires only, minimum damage levels); and delivered at your pull frequency, from near real-time polling to daily syncs. It is set up through a conversation with the Partner Success team, not a self-serve toggle.

If you are building internal tools, feeding an existing CRM or dispatch system, or pulling incident data at volume, a Custom API arrangement is built for exactly that. It is not a toggle in account settings — the FirstLeads team designs the feed around how your business actually operates.

Before your call, it helps to have rough answers to four questions — none of it needs to be locked in ahead of time; it is simply what the team will walk through with you.

What the team scopes with you

Geography

Which states, counties, cities, or ZIP codes you want data for. Access can be scoped as narrowly or as broadly as your territory requires.

Incident scope

Every incident in those areas, or a filtered subset — confirmed fires only, or Medium and High damage levels only. The team tunes this the same way Smart Filters and damage-level filters work elsewhere in FirstLeads.

Pull frequency

Near real-time polling, hourly batches, or a daily sync — the right setup depends on how your systems consume the data.

Everything else

Specific fields, data formats, volume requirements, or how the feed integrates with what you have already built. If you want the technical detail beforehand, the API documentation covers the offering in depth.

Talk through your data feed

Bring your geography, filters, and pull frequency to a call with Partner Success and get an API feed designed around your stack.

Book a Demo View Pricing

Frequently Asked Questions

Keep exploring

See everything the platform does on the FirstLeads features page.