How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →

Discovery

Learnings

Guidance

Toolbox

Alignment

API Evangelist LLC

Harbinger Health

Harbinger Health Users API

WordPress users resource routes.

Documentation Provider Profile APIs.io OpenAPI GitHub

Harbinger Health Users API is one of 37 APIs that Harbinger Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 21 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 2.0.0.

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

21 operations 6 paths 1 schemas 4 DELETE6 GET3 PATCH5 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification

OpenAPI 3.2.0

API Version

2.0.0

Base URL

https://harbinger-health.com/wp-json

Authentication

HTTP Basic

Contact

Harbinger Health

Resource Areas

1

Authentication & Security 1

Harbinger Health Users API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword).

applicationPassword — WordPress application password, advertised by the site's route-discovery document at authentication.application-passwords. Issued from https://harbinger-health…

Paths & Operations 21

Across 6 paths, the API surfaces 21 operations — 4 DELETE, 6 GET, 3 PATCH, 5 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

users 21

WordPress users resource routes.

GET

/wp/v2/users

GET /wp/v2/users

listUsers 15 params → 200400401404

POST

/wp/v2/users

POST /wp/v2/users

createUsers body → 200400401404

GET

/wp/v2/users/{id}

GET /wp/v2/users/{id}

getUsersById 2 params → 200400401404

POST

/wp/v2/users/{id}

POST /wp/v2/users/{id}

createUsersById 1 param body → 200400401404

PUT

/wp/v2/users/{id}

PUT /wp/v2/users/{id}

replaceUsersById 1 param body → 200400401404

PATCH

/wp/v2/users/{id}

PATCH /wp/v2/users/{id}

updateUsersById 1 param body → 200400401404

DELETE

/wp/v2/users/{id}

DELETE /wp/v2/users/{id}

deleteUsersById 3 params → 200400401404

GET

/wp/v2/users/{user_id}/application-passwords

GET /wp/v2/users/{userid}/application-passwords

getUsersByUserIdApplicationPasswords 2 params → 200400401404

POST

/wp/v2/users/{user_id}/application-passwords

POST /wp/v2/users/{userid}/application-passwords

createUsersByUserIdApplicationPasswords 1 param body → 200400401404

DELETE

/wp/v2/users/{user_id}/application-passwords

DELETE /wp/v2/users/{userid}/application-passwords

deleteUsersByUserIdApplicationPasswords 1 param → 200400401404

GET

/wp/v2/users/{user_id}/application-passwords/{uuid}

GET /wp/v2/users/{userid}/application-passwords/{uuid}

getUsersByUserIdApplicationPasswordsByUuid 3 params → 200400401404

POST

/wp/v2/users/{user_id}/application-passwords/{uuid}

POST /wp/v2/users/{userid}/application-passwords/{uuid}

createUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401404

PUT

/wp/v2/users/{user_id}/application-passwords/{uuid}

PUT /wp/v2/users/{userid}/application-passwords/{uuid}

replaceUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401404

PATCH

/wp/v2/users/{user_id}/application-passwords/{uuid}

PATCH /wp/v2/users/{userid}/application-passwords/{uuid}

updateUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401404

DELETE

/wp/v2/users/{user_id}/application-passwords/{uuid}

DELETE /wp/v2/users/{userid}/application-passwords/{uuid}

deleteUsersByUserIdApplicationPasswordsByUuid 2 params → 200400401404

GET

/wp/v2/users/{user_id}/application-passwords/introspect

GET /wp/v2/users/{userid}/application-passwords/introspect

getUsersByUserIdApplicationPasswordsIntrospect 2 params → 200400401404

GET

/wp/v2/users/me

GET /wp/v2/users/me

listUsersMe 1 param → 200400401404

POST

/wp/v2/users/me

POST /wp/v2/users/me

createUsersMe body → 200400401404

PUT

/wp/v2/users/me

PUT /wp/v2/users/me

replaceUsersMe body → 200400401404

PATCH

/wp/v2/users/me

PATCH /wp/v2/users/me

updateUsersMe body → 200400401404

DELETE

/wp/v2/users/me

DELETE /wp/v2/users/me

deleteUsersMe 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, observed live on this host.

3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

Other APIs Harbinger Health publishes across the network.

Harbinger Health MCP Server

AE Profile APIs.io

Harbinger Health Block Directory API

AE Profile APIs.io

Harbinger Health Block Patterns API

AE Profile APIs.io

Harbinger Health Block Renderer API

AE Profile APIs.io

Harbinger Health Block Types API

AE Profile APIs.io

Harbinger Health Blocks API

AE Profile APIs.io

Harbinger Health Categories API

AE Profile APIs.io

Harbinger Health Comments API

AE Profile APIs.io

Harbinger Health Events API

AE Profile APIs.io

Harbinger Health Font Collections API

AE Profile APIs.io

Harbinger Health Font Families API

AE Profile APIs.io

Harbinger Health Global Styles API

AE Profile APIs.io

#User

← Back to H APIs

Call it yourself

curl for this page

Search the network for this

curl "https://api.apievangelist.com/v1/search?q=harbinger-health-users-api&limit=10"

Everything under a tag

curl "https://api.apievangelist.com/v1/tags/harbinger-health-users-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Where this information came from

This is an independent, third-party profile of Harbinger Health Users 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.