Zenning APIzenning.ai ↗

Access all public pages from Zenning AI's website and retrieve detailed information including titles, metadata, headings, paragraphs, text, links, and images from any specific page. Browse the complete sitemap to discover available content and pull comprehensive page data for your needs.

Endpoint health

monitored

get_page

list_pages

Checks pendingself-healing

Endpoints

Updated

2h ago

This call costs2 credits / call— charged only on success

Try it

section

Site path prefix to filter by, with or without a leading slash, e.g. use-cases or /features/app-directory. Omitted = all pages.

→ api.parse.bot/scraper/35db3411-8773-44e6-90ec-50bc70f8d4e6/<endpoint>

Ready to send

Fill in the parameters and hit sign in to send to see live response data here.

Call it over HTTPgrab a free API key at signup

curl -X GET 'https://api.parse.bot/scraper/35db3411-8773-44e6-90ec-50bc70f8d4e6/list_pages?section=%2Ffeatures%2Fapp-directory' \
  -H 'X-API-Key: $PARSE_API_KEY'

All endpoints · 2 totalmissing one? ·

Returns every public page of the site as listed in its sitemap, one row per page, in sitemap order (roughly alphabetical by path). Each row carries the site-relative path (no trailing slash; the home page is '/'), the absolute URL, the top-level section (e.g. features, use-cases, company, user-guides, compare), the final slug and the depth. An optional section path prefix restricts the rows to that subtree (e.g. use-cases, or features/app-directory for the ~130 integration pages); total is the row count after filtering and site_total is the whole-site page count. A prefix that matches nothing yields an empty pages array. One round trip to the sitemap index plus one per sitemap file (currently one); ~200 pages.

Input

Param	Type	Description
section	string	Site path prefix to filter by, with or without a leading slash, e.g. use-cases or /features/app-directory. Omitted = all pages.

Response

{
  "type": "object",
  "fields": {
    "pages": "array of page rows: path (site-relative, feeds get_page), url, section (top-level path segment, 'home' for /), slug, depth (number of path segments)",
    "total": "number of rows returned after the section filter",
    "site_total": "number of distinct pages in the whole sitemap"
  },
  "sample": {
    "data": {
      "pages": [
        {
          "url": "https://zenning.ai/use-cases/customer-support",
          "path": "/use-cases/customer-support",
          "slug": "customer-support",
          "depth": 2,
          "section": "use-cases"
        },
        {
          "url": "https://zenning.ai/use-cases/data",
          "path": "/use-cases/data",
          "slug": "data",
          "depth": 2,
          "section": "use-cases"
        }
      ],
      "total": 8,
      "site_total": 208
    },
    "status": "success"
  }
}

About the Zenning API

The Zenning API on Parse exposes 2 endpoints for the publicly available data on zenning.ai. Calls return JSON over HTTPS and are billed per successful response.

Pin a release with the API-Snapshot-Version header so canonical updates don't silently change your contract.