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

X-WP-Total

Representation Metadata de facto — unregistered response

A reference entry. The registry facts and catalog measurements below are complete; the written guidance for this header has not been authored yet.

The X-WP-Total HTTP header — representation metadata, declared by 55 providers in the API Evangelist catalog.

X-WP-Total is representation metadata — Headers describing the payload itself — its type, length, encoding, disposition, location.

The registry

Not registered with IANA. It is a de facto or vendor field — real, widely used, and governed by nothing but convention.

In the catalog

Declared by 55 providers across 1,114 published specification files in the API Evangelist catalog, where it appears as a response header — sent by the server.

Governed by these rules

Machine-enforceable governance rules from rules.apievangelist.com that apply to this header when it appears in an OpenAPI.

OpenAPI Components Headers Error error

Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses

Guidance: Rate Limits →
OpenAPI Components Headers Info info

Utilizing the headers object in the centralized OpenAPI components library helps make headers reusable across API requests and responses

Guidance: Rate Limits →
OpenAPI Headers Hyphenated Pascal Case error

HTTP headers should follow Hyphenated-Pascal-Case naming convention for consistency and readability, such as Content-Type, X-Request-Id, or Accept-Language.

Guidance: Naming →