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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
LIVEKINDLY

LIVEKINDLY Users API

The Users API from LIVEKINDLY — 6 operation(s) for users.

Documentation Provider Profile APIs.io OpenAPI GitHub

LIVEKINDLY Users API is one of 13 APIs that LIVEKINDLY 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 15 operations across 6 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version wp/v2.

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

15 operations 6 paths 1 schemas 4 DELETE6 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
wp/v2
Base URL
https://thelivekindlyco.com/wp-json/wp/v2
Authentication
HTTP Basic, API Key
Contact
LIVEKINDLY Collective
Resource Areas
1

Authentication & Security 2

LIVEKINDLY Users 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).

  • applicationPassword — WordPress Application Passwords over HTTP Basic. Issued from https://thelivekindlyco.com/wp-admin/authorize-application.php.
  • cookieNonce — Logged-in cookie authentication with an X-WP-Nonce header (browser context only).

Paths & Operations 15

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

Users 15
GET
/wp/v2/users
GET /wp/v2/users
getUsers 15 params → 200400401403404
POST
/wp/v2/users
POST /wp/v2/users
createUsers body → 200400401403404
GET
/wp/v2/users/{id}
GET /wp/v2/users/(?P [\d]+)
getUsersById 3 params → 200400401403404
POST
/wp/v2/users/{id}
POST /wp/v2/users/(?P [\d]+)
createUsersById 1 param body → 200400401403404
DELETE
/wp/v2/users/{id}
DELETE /wp/v2/users/(?P [\d]+)
deleteUsersById 4 params → 200400401403404
GET
/wp/v2/users/{user_id}/application-passwords
GET /wp/v2/users/(?P (?:[\d]+|me))/application-passwords
getUsersByUserIdApplicationPasswords 2 params → 200400401403404
POST
/wp/v2/users/{user_id}/application-passwords
POST /wp/v2/users/(?P (?:[\d]+|me))/application-passwords
createUsersByUserIdApplicationPasswords 1 param body → 200400401403404
DELETE
/wp/v2/users/{user_id}/application-passwords
DELETE /wp/v2/users/(?P (?:[\d]+|me))/application-passwords
deleteUsersByUserIdApplicationPasswords 1 param → 200400401403404
GET
/wp/v2/users/{user_id}/application-passwords/{uuid}
GET /wp/v2/users/(?P (?:[\d]+|me))/application-passwords/(?P [\w\-]+)
getUsersByUserIdApplicationPasswordsByUuid 3 params → 200400401403404
POST
/wp/v2/users/{user_id}/application-passwords/{uuid}
POST /wp/v2/users/(?P (?:[\d]+|me))/application-passwords/(?P [\w\-]+)
createUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401403404
DELETE
/wp/v2/users/{user_id}/application-passwords/{uuid}
DELETE /wp/v2/users/(?P (?:[\d]+|me))/application-passwords/(?P [\w\-]+)
deleteUsersByUserIdApplicationPasswordsByUuid 2 params → 200400401403404
GET
/wp/v2/users/{user_id}/application-passwords/introspect
GET /wp/v2/users/(?P (?:[\d]+|me))/application-passwords/introspect
getUsersByUserIdApplicationPasswordsIntrospect 2 params → 200400401403404
GET
/wp/v2/users/me
GET /wp/v2/users/me
getUsersMe 1 param → 200400401403404
POST
/wp/v2/users/me
POST /wp/v2/users/me
createUsersMe body → 200400401403404
DELETE
/wp/v2/users/me
DELETE /wp/v2/users/me
deleteUsersMe 2 params → 200400401403404

Schemas 1

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

Error
object
The WordPress REST error envelope. Not RFC 9457 problem+json.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

livekindly-users-api-openapi.yml Raw ↑

Other APIs LIVEKINDLY publishes across the network.

LIVEKINDLY MCP Server (WordPress MCP Adapter)
AE Profile APIs.io
LIVEKINDLY Brands API
AE Profile APIs.io
LIVEKINDLY Careers API
AE Profile APIs.io
LIVEKINDLY Comments API
AE Profile APIs.io
LIVEKINDLY Discovery API
AE Profile APIs.io
LIVEKINDLY Media API
AE Profile APIs.io
LIVEKINDLY Pages API
AE Profile APIs.io
LIVEKINDLY Partners API
AE Profile APIs.io
LIVEKINDLY Posts API
AE Profile APIs.io
LIVEKINDLY Search API
AE Profile APIs.io
LIVEKINDLY Settings API
AE Profile APIs.io
LIVEKINDLY Taxonomy API
AE Profile APIs.io
#User
← Back to L APIs
API Details
ID
livekindly:livekindly-users-api
Base URL
https://thelivekindlyco.com/wp-json/wp/v2
Docs
https://thelivekindlyco.com/latest-news/
Provider
LIVEKINDLY
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=livekindly-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/livekindly-users-api"

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

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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