Webz.io logoDocs
Overview
Start Here
News, Blogs, Forums & Reviews APIs
News Search API
Firehose
Cyber API
Introduction
Quickstart
Filters
Post Data Fields
SOCMint API
API Reference
Query Syntax
Time Range
Endpoints & Authentication
Request Parameters
Response Format
Pagination
Segmentation API
Dark Cache & Images
Errors, Rate Limits & Credits
FAQ
Data Breaches API
News, Blogs, Forums & Reviews Archive
Web Content API (Deprecated)
Webz.io logo
Overview
Start Here
News, Blogs, Forums & Reviews APIs
News Search API
Firehose
Cyber API
Introduction
Quickstart
Filters
Post Data Fields
SOCMint API
API Reference
Query Syntax
Time Range
Endpoints & Authentication
Request Parameters
Response Format
Pagination
Segmentation API
Dark Cache & Images
Errors, Rate Limits & Credits
FAQ
Data Breaches API
News, Blogs, Forums & Reviews Archive
Web Content API (Deprecated)

On this page

No sections

Webz.io DocumentationContact our team© 2026

Pagination

Every search response includes a next field - a ready-made relative URL for the next page. You never need to build paging parameters yourself.

The loop

  1. Send your first request.
  2. Fetch the results from the cyberDocs array.
  3. Append next to https://api.webz.io and call it.
  4. Repeat until moreResultsAvailable reaches 0.
json
{
  "cyberDocs": [ ... ],
  "next": "/cyberFilter?token=YOUR_TOKEN&format=json&ts=1751630400000&q=bitcoin",
  "moreResultsAvailable": 4200
}

Following new content over time

With the default crawled sort, next carries your position forward in time. Keep calling it on a schedule and you receive only posts crawled since your last call.

Offset sorts

With published, thread.published, or relevancy sorts, next advances an offset (from) instead of a time cursor.

Each page is a new request and consumes a credit - see Errors, Rate Limits & Credits.

Last updated: July 28, 2026
PreviousResponse FormatNextSegmentation API