Heuritech Pages API
The 63 published marketing, product, pricing, FAQ and legal pages that make up heuritech.com, served as JSON by the WordPress REST API. Derived by API Evangelist from the live route-discovery document.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/heuritech-pages-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Heuritech Content API (WordPress REST wp/v2) Pages API
version: wp/v2
summary: 'Public read surface of the heuritech.com content estate: blog posts, pages, media, comments, taxonomy, authors and site search.'
description: 'Heuritech publishes heuritech.com on WordPress (WordPress.com Atomic + Jetpack), which exposes the WordPress REST API at https://heuritech.com/wp-json/. The wp/v2 namespace is anonymously readable and returns the company blog, marketing and legal pages, media library, reader comments, editorial taxonomy, author profiles and a site-wide search endpoint as JSON.
This document was DERIVED mechanically by API Evangelist from the route-discovery document served at https://heuritech.com/wp-json/ on 2026-08-17 — every path, method and parameter below is taken verbatim from that descriptor. Heuritech publishes no OpenAPI definition of its own, and this is NOT the Heuritech product API: the commercial Heuritech trend-data API is sold on the Business and Enterprise plans and has no public documentation, base URL or specification. Only GET operations are modelled here; the write operations WordPress registers on these same routes require authentication (WordPress Application Passwords over HTTP Basic).'
contact:
name: Heuritech
url: https://heuritech.com/
x-derived-by: API Evangelist enrichment pipeline
x-derived-from: https://heuritech.com/wp-json/
x-derived-on: '2026-08-17'
x-provider-published: false
servers:
- url: https://heuritech.com/wp-json
description: Production
tags:
- name: Pages
description: The 63 published marketing, product, legal and company pages that make up heuritech.com.
paths:
/wp/v2/pages:
get:
operationId: getPages
summary: GET /wp/v2/pages
description: The 63 published marketing, product, legal and company pages that make up heuritech.com.
tags:
- Pages
parameters:
- name: after
in: query
required: false
schema:
type: string
format: date-time
description: Limit response to posts published after a given ISO8601 compliant date.
- name: author
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Limit result set to posts assigned to specific authors.
- name: author_exclude
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Ensure result set excludes posts assigned to specific authors.
- name: before
in: query
required: false
schema:
type: string
format: date-time
description: Limit response to posts published before a given ISO8601 compliant date.
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
- name: exclude
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Ensure result set excludes specific IDs.
- name: include
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Limit result set to specific IDs.
- name: menu_order
in: query
required: false
schema:
type: integer
description: Limit result set to posts with a specific menu_order value.
- name: modified_after
in: query
required: false
schema:
type: string
format: date-time
description: Limit response to posts modified after a given ISO8601 compliant date.
- name: modified_before
in: query
required: false
schema:
type: string
format: date-time
description: Limit response to posts modified before a given ISO8601 compliant date.
- name: offset
in: query
required: false
schema:
type: integer
description: Offset the result set by a specific number of items.
- name: order
in: query
required: false
schema:
type: string
enum:
- asc
- desc
default: desc
description: Order sort attribute ascending or descending.
- name: orderby
in: query
required: false
schema:
type: string
enum:
- author
- date
- id
- include
- modified
- parent
- relevance
- slug
- include_slugs
- title
- menu_order
default: date
description: Sort collection by post attribute.
- name: orderby_hierarchy
in: query
required: false
schema:
type: boolean
default: false
description: Sort pages by hierarchy.
- name: page
in: query
required: false
schema:
type: integer
default: 1
minimum: 1
description: Current page of the collection.
- name: parent
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Limit result set to items with particular parent IDs.
- name: parent_exclude
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Limit result set to all items except those of a particular parent ID.
- name: per_page
in: query
required: false
schema:
type: integer
default: 10
minimum: 1
maximum: 100
description: Maximum number of items to be returned in result set.
- name: search
in: query
required: false
schema:
type: string
description: Limit results to those matching a string.
- name: search_columns
in: query
required: false
schema:
type: array
default: []
items:
type: string
enum:
- post_title
- post_content
- post_excerpt
description: Array of column names to be searched.
- name: search_semantics
in: query
required: false
schema:
type: string
enum:
- exact
description: How to interpret the search input.
- name: slug
in: query
required: false
schema:
type: array
items:
type: string
description: Limit result set to posts with one or more specific slugs.
- name: status
in: query
required: false
schema:
type: array
default: publish
items:
type: string
enum:
- publish
- future
- draft
- pending
- private
- trash
- auto-draft
- inherit
- request-pending
- request-confirmed
- request-failed
- request-completed
- acf-disabled
- any
description: Limit result set to posts assigned one or more statuses.
responses:
'200':
description: Success. Collection responses carry X-WP-Total and X-WP-TotalPages headers.
headers:
X-WP-Total:
description: Total number of items in the collection.
schema:
type: integer
X-WP-TotalPages:
description: Total number of pages available.
schema:
type: integer
content:
application/json:
schema:
type: array
items:
type: object
'400':
description: 'Invalid parameter. WordPress error envelope: {code, message, data:{status}}.'
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'401':
description: Authentication required for this context or resource (rest_forbidden / rest_cannot_read).
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'404':
description: No route or resource matched the request (rest_no_route / rest_post_invalid_id).
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
/wp/v2/pages/{id}:
get:
operationId: getPagesId
summary: GET /wp/v2/pages/{id}
description: The 63 published marketing, product, legal and company pages that make up heuritech.com.
tags:
- Pages
parameters:
- name: id
in: path
required: true
schema:
type: integer
description: Unique identifier for the post.
- name: context
in: query
required: false
schema:
type: string
enum:
- view
- embed
- edit
default: view
description: Scope under which the request is made; determines fields present in response.
- name: excerpt_length
in: query
required: false
schema:
type: integer
description: Override the default excerpt length.
- name: password
in: query
required: false
schema:
type: string
description: The password for the post if it is password protected.
responses:
'200':
description: Success. Collection responses carry X-WP-Total and X-WP-TotalPages headers.
headers:
X-WP-Total:
description: Total number of items in the collection.
schema:
type: integer
X-WP-TotalPages:
description: Total number of pages available.
schema:
type: integer
content:
application/json:
schema:
type: object
'400':
description: 'Invalid parameter. WordPress error envelope: {code, message, data:{status}}.'
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'401':
description: Authentication required for this context or resource (rest_forbidden / rest_cannot_read).
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
'404':
description: No route or resource matched the request (rest_no_route / rest_post_invalid_id).
content:
application/json:
schema:
$ref: '#/components/schemas/WPError'
components:
schemas:
WPError:
type: object
description: The WordPress REST API error envelope returned on every 4xx/5xx.
properties:
code:
type: string
description: Machine-readable error code, e.g. rest_no_route.
message:
type: string
description: Human-readable error message.
data:
type: object
properties:
status:
type: integer
required:
- code
- message