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

Labayh Meta API

Discovery, registered types, taxonomies, statuses and cross-content search.

Labayh Meta API is one of 7 APIs that Labayh publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Meta. The published artifact set on APIs.io includes an OpenAPI specification and 1 JSON Schema.

This API exposes 5 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version wp/v2.

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

5 operations 5 paths 6 schemas 5 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
wp/v2
Base URL
https://labayh.net/wp-json
Authentication
HTTP Basic, API Key
Contact
Terms of Service
Resource Areas
1

Authentication & Security 2

Labayh Meta API declares 2 security schemes for authenticating requests. It accepts HTTP basic authentication (applicationPassword). An API key is passed in the header as X-WP-Nonce (cookieNonce). By default, every request must be authenticated.

  • applicationPassword — WordPress application passwords, advertised by the API index at https://labayh.net/wp-json/ (authorization endpoint: https://labayh.net/wp-admin/authorize-appl…
  • cookieNonce — Cookie-authenticated first-party requests pass a nonce in the X-WP-Nonce header.

Paths & Operations 5

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

Meta 5

Discovery, registered types, taxonomies, statuses and cross-content search.

GET
/wp/v2/types
List types
listTypes 1 param → 200400
GET
/wp/v2/taxonomies
List taxonomies
listTaxonomies 2 params → 200400
GET
/wp/v2/statuses
List statuses
listStatuses 1 param → 200400
GET
/wp/v2/search
List search
listSearch 8 params → 200400
GET
/
Retrieve the API discovery index
getApiIndex → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ContentType (16 properties), Taxonomy (11 properties), ContentStatus (8 properties), ApiIndex (7 properties). Each schema is shown below with its type and property counts.

SearchResult
object
5 properties
ApiIndex
object
7 properties
ContentType
object
16 properties
ContentStatus
object
8 properties
Error
object
The WordPress REST error envelope returned on every 4xx/5xx response.
3 properties
Taxonomy
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

labayh-meta-api-openapi.yml Raw ↑

Other APIs Labayh publishes across the network.

Labayh Consultants API
Labayh Content API
Labayh Events API
Labayh Programs API
Labayh Support Groups API
Labayh Webinars API
Where this information came from

This is an independent, third-party profile of Labayh Meta 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.