Curated Feed

Webz.io offers access to data through topical Firehose feeds delivered via a RESTful API, without any limits on the number of API calls.
Instead of querying for specific results, clients receive all relevant, enriched data in real time through persistent, topic-based feeds, ensuring complete coverage with low latency.

FH Endpoint

Unlike the live NBDR API, which lets users create custom queries with each API call, the Firehose (FH) API works differently. Each FH API endpoint comes pre-configured with filters based on the user's needs, delivering a continuous stream of matching data, no need to send new queries.

Endpoint structure

https://api.webz.io/firehose?token=[FH_CLIENT_TOKEN]&client_feed=[FH_CLIENT_NAME]

https://api.webz.io/firehose?token=xxxxxxxxxxx&client_feed=fh_webz_client

Pagination

Each page contains 100 posts. To fetch the next page, it is required to make a new API call which contains the Endpoint's base + the value of the 'nextPage' field at the end of each response.

For example:

// Original Endpoint:
https://api.webz.io/firehose?token=xxxxxxx&client_feed=fh_webz_client

// nextPage field at the end of each JSON response
"nextPage": "/firehose?token=xxxx&client_feed=fh_webz_client&since=1753090852000&nid=8190f1a6134741e150dfb86278365a834f4985d0"

// For next API call, we use the Endpoint base with the new nextPage value
https://api.webz.io/firehose?token=xx&client_feed=fh_webz_client&since=1753090852000&nid=8190f1a6134741e150dfb86278365a834f4985d0

https://api.webz.io/firehose?token=xxxxx&client_feed=fh_webz_client

To learn more on Pagination visit this page.

👍

Note

Latency - Data is typically available in the API ~5 minutes after crawling.

Rate - The recommended best practice is 1 API call per second. However, higher rates can be supported through predefined configurations, which require prior coordination with our Customer Support team.

Order - Posts are sorted chronologically, from oldest to newest.

Code Example

Review and download our best practice code from here.