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

Allotex Discovery API

Route index, cross-content search and the oEmbed provider endpoint.

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

Tagged areas include Discovery. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, and a JSON-LD context.

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

Requests are made against 2 base URLs: https://us.allotex.com/wp-json, https://allotex.com/wp-json.

4 operations 4 paths 4 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://us.allotex.com/wp-json
Authentication
HTTP Basic
License
GPL-2.0-or-later
Resource Areas
1

Authentication & Security 1

Allotex Discovery API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword).

  • applicationPassword — WordPress application passwords, the only authentication method the route index advertises (authorization endpoint: https://us.allotex.com/wp-admin/authorize-a…

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.

discovery 4

Route index, cross-content search and the oEmbed provider endpoint.

GET
/
Get the API route index
getRouteIndex 2 params → 200404
GET
/wp/v2/search
Search across content types
searchContent 9 params → 200400
GET
/oembed/1.0/embed
Get an oEmbed response for a site URL
getOEmbed 3 params → 200404
GET
/mcp
Get the MCP namespace route index
getMcpNamespaceIndex 1 param → 200

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are OEmbed (10 properties), RouteIndex (9 properties), SearchResult (6 properties), RestError (3 properties). Each schema is shown below with its type and property counts.

RouteIndex
object
The WordPress REST API discovery document.
9 properties
RestError
object
The WordPress REST error envelope. NOT RFC 9457 — the media type is application/json, not application/problem+json, and the field names are code/message/data.s…
3 properties 3 required
OEmbed
object
10 properties
SearchResult
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

allotex-discovery-api-openapi.yml Raw ↑

Other APIs Allotex publishes across the network.

Allotex Content API
Allotex Identity API
Allotex Media API
Allotex Schema API
Allotex Taxonomy API
Where this information came from

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