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

Abcuro Pages API

Static site pages.

Abcuro Pages API is one of 12 APIs that Abcuro publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Pages. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

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

2 operations 2 paths 2 schemas 2 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://abcuro.com/wp-json/
Authentication
HTTP Basic, API Key
Resource Areas
1

Authentication & Security 2

Abcuro Pages 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, though some operations may also be called without credentials.

  • applicationPassword — WordPress application passwords (RFC 7617 Basic over TLS). The live route index advertises the authorization endpoint at https://abcuro.com/wp-admin/authorize-…
  • cookieNonce — WordPress cookie authentication paired with an X-WP-Nonce header; used by the site's own admin and block-editor UI.

Paths & Operations 2

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

Pages 2

Static site pages.

GET
/wp/v2/pages
List pages
listPages 22 params → 200400401403
GET
/wp/v2/pages/{id}
Get a single page
getPage 5 params → 200400401403404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are Page (25 properties), Error (3 properties). Each schema is shown below with its type and property counts.

Page
object
A page record as returned by the Abcuro WordPress REST API. Field set derived from live responses fetched 2026-08-02.
25 properties
Error
object
The WordPress REST API error envelope. This is NOT RFC 9457 problem+json — errors are returned as application/json with a machine-readable string code.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

abcuro-pages-api-openapi.yml Raw ↑

Other APIs Abcuro publishes across the network.

Abcuro Careers API
Abcuro Comments API
Abcuro Discovery API
Abcuro Investors API
Abcuro Media API
Abcuro People API
Abcuro Press Releases API
Abcuro Publications API
Abcuro Search API
Abcuro Taxonomy API
Abcuro Users API
Where this information came from

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