Heuritech Comments API
The 1,284 reader comments attached to Heuritech blog posts, anonymously readable as JSON by post, author or date range.
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-comments-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) Comments 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: Comments
description: The 1,284 reader comments attached to Heuritech blog posts.
paths:
/wp/v2/comments:
get:
operationId: getComments
summary: GET /wp/v2/comments
description: The 1,284 reader comments attached to Heuritech blog posts.
tags:
- Comments
parameters:
- name: after
in: query
required: false
schema:
type: string
format: date-time
description: Limit response to comments published after a given ISO8601 compliant date.
- name: author
in: query
required: false
schema:
type: array
items:
type: integer
description: Limit result set to comments assigned to specific user IDs. Requires authorization.
- name: author_email
in: query
required: false
schema:
type: string
format: email
description: Limit result set to that from a specific author email. Requires authorization.
- name: author_exclude
in: query
required: false
schema:
type: array
items:
type: integer
description: Ensure result set excludes comments assigned to specific user IDs. Requires authorization.
- name: before
in: query
required: false
schema:
type: string
format: date-time
description: Limit response to comments 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: 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:
- date
- date_gmt
- id
- include
- post
- parent
- type
default: date_gmt
description: Sort collection by comment attribute.
- 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 comments of specific parent IDs.
- name: parent_exclude
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Ensure result set excludes specific parent IDs.
- name: password
in: query
required: false
schema:
type: string
description: The password for the post if it is password protected.
- 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: post
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Limit result set to comments assigned to specific post IDs.
- name: search
in: query
required: false
schema:
type: string
description: Limit results to those matching a string.
- name: status
in: query
required: false
schema:
type: string
default: approve
description: Limit result set to comments assigned a specific status. Requires authorization.
- name: type
in: query
required: false
schema:
type: string
default: comment
description: Limit result set to comments assigned a specific type. Requires authorization.
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/comments/{id}:
get:
operationId: getCommentsId
summary: GET /wp/v2/comments/{id}
description: The 1,284 reader comments attached to Heuritech blog posts.
tags:
- Comments
parameters:
- name: id
in: path
required: true
schema:
type: integer
description: Unique identifier for the comment.
- 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: password
in: query
required: false
schema:
type: string
description: The password for the parent post of the comment (if the post 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