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 API Discovery

The self-describing routes of the deployment — registered post types, taxonomies and post statuses, plus the route index at the server root that publishes name, description, namespaces, all 150 routes and the application-passwords authentication block.

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

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

This API exposes 6 operations across 6 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.

6 operations 6 paths 1 schemas 6 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 6

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

discovery 6

Post types, taxonomies and statuses — the self-describing surface of the deployment.

GET
/wp/v2/types
List registered post types
listTypes 1 param → 200400401404
GET
/wp/v2/types/{type}
Retrieve a single post type
getType 2 params → 200400401404
GET
/wp/v2/taxonomies
List registered taxonomies
listTaxonomies 2 params → 200400401404
GET
/wp/v2/taxonomies/{taxonomy}
Retrieve a single taxonomy
getTaxonomy 2 params → 200400401404
GET
/wp/v2/statuses
List post statuses
listStatuses 1 param → 200400401404
GET
/wp/v2/statuses/{status}
Retrieve a single post status
getStatus 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-discovery-api-openapi.yml Raw ↑

Other APIs LEAF4Life publishes across the network.

LEAF4Life Content Pages API
LEAF4Life Media API
LEAF4Life Taxonomy API
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 API Discovery, 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.