How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

LEAF4Life Taxonomy API

Category and tag terms. Registered and anonymously reachable but effectively unused — one category (the WordPress default `uncategorized`) and 21 tags, every one with an item count of zero, and the tag slugs are theme-demo residue rather than company vocabulary.

LEAF4Life Taxonomy API is one of 9 APIs that LEAF4Life publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Taxonomy. The published artifact set on APIs.io includes an OpenAPI specification and authentication docs.

This API exposes 4 operations across 4 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

Requests are made against a single base URL, https://leafforlife.com/wp-json.

4 operations 4 paths 1 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://leafforlife.com/wp-json
Resource Areas
1

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

taxonomy 4

Category and tag terms — 1 category and 21 tags, every one with a zero item count.

GET
/wp/v2/categories
List categories
listCategories 12 params → 200400401404
GET
/wp/v2/categories/{id}
Retrieve a single category
getCategory 2 params → 200400401404
GET
/wp/v2/tags
List tags
listTags 12 params → 200400401404
GET
/wp/v2/tags/{id}
Retrieve a single tag
getTag 2 params → 200400401404

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is WPError (3 properties). Each schema is shown below with its type and property counts.

WPError
object
The WordPress REST error envelope. Not RFC 9457 problem+json; served as application/json.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

leaf4life-taxonomy-api-openapi.yml Raw ↑

Other APIs LEAF4Life publishes across the network.

LEAF4Life Content Pages API
LEAF4Life Media API
LEAF4Life API Discovery
LEAF4Life Search API
LEAF4Life Authors API
LEAF4Life Posts and Comments API
LEAF4Life oEmbed API
LEAF4Life Comments API
Where this information came from

This is an independent, third-party profile of LEAF4Life Taxonomy API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.