Webz.io provides machine-defined web data: web content collected at scale, normalized, enriched with metadata, and delivered through machine-readable data feeds and APIs. Webz.io crawls the web so your systems do not have to - instead of building and maintaining crawlers, parsers, source monitoring, deduplication, enrichment, and delivery pipelines yourself, you query Webz.io and receive structured data your application can process.
Use Webz.io when your product, research workflow, model, dashboard, or security program needs current or historical web data in a predictable format. Typical use cases include marketing technology, financial analysis, cybersecurity, market research, machine learning, media monitoring, brand intelligence, and risk analysis.
Webz.io works across open, deep, and dark web sources. The exact API you choose depends on the data you need:
| Need | Use | Example result |
|---|---|---|
| News coverage | News API | Structured article text, title, URL, publisher, language, country, entities, and crawl metadata. |
| Semantic news discovery | News Search API | Articles matched by meaning, with summaries, relevant text excerpts, language, country, category, sentiment, and source metadata. |
| Blog posts | Blogs API | Structured posts from blogs and self-published sites. |
| Online discussions | Forums API | Threads, posts, replies, authors, and discussion metadata from forums and message boards. |
| Customer feedback | Reviews API | Reviews, ratings, reviewed items, authors, language, dates, and source details. |
| Cyber threat intelligence | Cyber API | Deep and dark web posts, threat actor discussions, leaked references, domains, hashes, CVEs, and enrichments. |
| Compromised credentials | Data Breaches API | Email, username, password, source, breach, and device context for exposed records. |
| Historical datasets | Archive | A downloadable dataset for a query and time range when you need more history than live APIs return. |
The value is not only collection. Raw web pages are inconsistent - every site has its own layout, date format, author format, language, and noise. Webz.io normalizes that content into structured JSON fields so your code can search, filter, paginate, analyze, store, or feed it into downstream systems.
Most Webz.io APIs are HTTP GET endpoints. You authenticate with your private API token, pass a query in q, and receive JSON by default. The query language supports free text, phrases, Boolean logic, and field filters.
A simple News API request:
https://api.webz.io/api/news?token=YOUR_TOKEN&q="artificial intelligence"
A Blogs API request using a language filter:
https://api.webz.io/api/blogs?token=YOUR_TOKEN&q=language:english ("electric vehicles" OR ev)
A Forums API request for active discussions:
https://api.webz.io/api/forums?token=YOUR_TOKEN&q=title:postgresql OR text:postgresql
A Reviews API request for high-rated reviews:
https://api.webz.io/reviewFilter?token=YOUR_TOKEN&q=rating:>=4 language:english "noise cancelling"
A Cyber API request for dark web mentions of bitcoin:
https://api.webz.io/cyberFilter?token=YOUR_TOKEN&q=bitcoin&size=10
A Data Breaches API request scoped to a domain:
https://api.webz.io/breaches?token=YOUR_TOKEN&email_domain=example.com
Replace YOUR_TOKEN with the token from your Webz.io dashboard, and URL-encode the q value in real requests. Access is product-specific, so a token must be enabled for the API you call.
Each product has its own response shape, but the pattern is consistent: a collection of matching records plus pagination and account metadata. For News, Blogs & Forums the main list is posts; for Reviews it is reviews; for Cyber it is cyberDocs; for Data Breaches it is records.
A simplified News API response looks like this:
{
"posts": [
{
"uuid": "6bd4f2f1a2...",
"url": "https://www.example.com/article",
"title": "Example headline",
"text": "Full extracted text of the post...",
"language": "english",
"published": "2026-07-06T07:00:00.000+0000",
"thread": {
"site_full": "example.com",
"site_type": "news",
"country": "US"
}
}
],
"total_results": 1234,
"more_results_available": 1134,
"next": "/api/news?q=...&ts=1751713632000&ni=6bd4f2..."
}When next is present, use it to fetch the next page: append it to https://api.webz.io and call it again. Do not build pagination cursors yourself.
Start with the question you need to answer:
| Question | Recommended starting point |
|---|---|
| "What is being reported by media outlets right now?" | News API |
| "Which news articles best match a topic or question by meaning?" | News Search API |
| "What are people writing in blogs or niche publications?" | Blogs API |
| "What are users discussing in forums and message boards?" | Forums API |
| "What do customers say about a product, service, hotel, app, or marketplace item?" | Reviews API |
| "What threats, leaked data, or suspicious mentions appear in dark web sources?" | Cyber API |
| "Which compromised accounts are exposed for a domain or email?" | Data Breaches API |
| "I need older data or a full historical dataset." | Archive |
| "I need high-volume continuous delivery rather than request/response search." | Firehose or a curated feed |
If you are unsure, start with the API closest to the source type. News, Blogs, and Forums share the same modern endpoint family and response model, so moving between them is straightforward. Reviews, Cyber, Data Breaches, Archive, and Firehose solve different data problems and have their own response formats, limits, and billing rules.
For a first technical path, go to News, Blogs & Forums APIs if you need open web content, Cyber API if you need dark web intelligence, or Data Breaches API if you need compromised credential records.