Heuritech Taxonomy API
The five editorial categories Heuritech uses to classify its blog content, plus the (currently empty) tag taxonomy, served as JSON by the WordPress REST API.
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-taxonomy-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) Taxonomy 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: Taxonomy
description: The five editorial categories used to classify Heuritech blog content, plus the (currently empty) tag taxonomy.
paths:
/wp/v2/categories:
get:
operationId: getCategories
summary: GET /wp/v2/categories
description: The five editorial categories used to classify Heuritech blog content, plus the (currently empty) tag taxonomy.
tags:
- Taxonomy
parameters:
- 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: hide_empty
in: query
required: false
schema:
type: boolean
default: false
description: Whether to hide terms not assigned to any posts.
- name: include
in: query
required: false
schema:
type: array
default: []
items:
type: integer
description: Limit result set to specific IDs.
- name: order
in: query
required: false
schema:
type: string
enum:
- asc
- desc
default: asc
description: Order sort attribute ascending or descending.
- name: orderby
in: query
required: false
schema:
type: string
enum:
- id
- include
- name
- slug
- include_slugs
- term_group
- description
- count
default: name
description: Sort collection by term 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: integer
description: Limit result set to terms assigned to a specific parent.
- 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: integer
description: Limit result set to terms assigned to a specific post.
- name: search
in: query
required: false
schema:
type: string
description: Limit results to those matching a string.
- name: slug
in: query
required: false
schema:
type: array
items:
type: string
description: Limit result set to terms with one or more specific slugs.
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/categories/{id}:
get:
operationId: getCategoriesId
summary: GET /wp/v2/categories/{id}
description: The five editorial categories used to classify Heuritech blog content, plus the (currently empty) tag taxonomy.
tags:
- Taxonomy
parameters:
- name: id
in: path
required: true
schema:
type: integer
description: Unique identifier for the term.
- 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.
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'
/wp/v2/tags:
get:
operationId: getTags
summary: GET /wp/v2/tags
description: The five editorial categories used to classify Heuritech blog content, plus the (currently empty) tag taxonomy.
tags:
- Taxonomy
parameters:
- 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: hide_empty
in: query
required: false
schema:
type: boolean
default: false
description: Whether to hide terms not assigned to any posts.
- 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: asc
description: Order sort attribute ascending or descending.
- name: orderby
in: query
required: false
schema:
type: string
enum:
- id
- include
- name
- slug
- include_slugs
- term_group
- description
- count
default: name
description: Sort collection by term attribute.
- name: page
in: query
required: false
schema:
type: integer
default: 1
minimum: 1
description: Current page of the collection.
- 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: integer
description: Limit result set to terms assigned to a specific post.
- name: search
in: query
required: false
schema:
type: string
description: Limit results to those matching a string.
- name: slug
in: query
required: false
schema:
type: array
items:
type: string
description: Limit result set to terms with one or more specific slugs.
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/tags/{id}:
get:
operationId: getTagsId
summary: GET /wp/v2/tags/{id}
description: The five editorial categories used to classify Heuritech blog content, plus the (currently empty) tag taxonomy.
tags:
- Taxonomy
parameters:
- name: id
in: path
required: true
schema:
type: integer
description: Unique identifier for the term.
- 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.
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