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
Vestaron

Vestaron Users API

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

Documentation Provider Profile APIs.io OpenAPI GitHub

Vestaron Users API is one of 10 APIs that Vestaron 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 and authentication docs.

This API exposes 21 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://vestaron.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
wp/v2
Base URL
https://vestaron.com/wp-json/wp/v2
Authentication
HTTP Basic
Contact
Vestaron
Resource Areas
1

Authentication & Security 1

Vestaron Users API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (applicationPassword). By default, every request must be authenticated, though some operations may also be called without credentials.

  • applicationPassword — WordPress Application Passwords over HTTP Basic. The application-password routes are registered on vestaron.com (/wp/v2/users/{userid}/application-passwords),…

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
GET
/wp/v2/users
GET /wp/v2/users
getUsers 15 params → 200404400401
POST
/wp/v2/users
POST /wp/v2/users
createUsers body → 200400401403404
GET
/wp/v2/users/{id}
GET /wp/v2/users/{id}
getUsersById 2 params → 200404400401
POST
/wp/v2/users/{id}
POST /wp/v2/users/{id}
createUsersById 1 param body → 200400401403404
PUT
/wp/v2/users/{id}
PUT /wp/v2/users/{id}
updateUsersById 1 param body → 200400401403404
PATCH
/wp/v2/users/{id}
PATCH /wp/v2/users/{id}
patchUsersById 1 param body → 200400401403404
DELETE
/wp/v2/users/{id}
DELETE /wp/v2/users/{id}
deleteUsersById 3 params → 200400401403404
GET
/wp/v2/users/{user_id}/application-passwords
GET /wp/v2/users/{userid}/application-passwords
getUsersByUserIdApplicationPasswords 2 params → 200404400401
POST
/wp/v2/users/{user_id}/application-passwords
POST /wp/v2/users/{userid}/application-passwords
createUsersByUserIdApplicationPasswords 1 param body → 200400401403404
DELETE
/wp/v2/users/{user_id}/application-passwords
DELETE /wp/v2/users/{userid}/application-passwords
deleteUsersByUserIdApplicationPasswords 1 param → 200400401403404
GET
/wp/v2/users/{user_id}/application-passwords/{uuid}
GET /wp/v2/users/{userid}/application-passwords/{uuid}
getUsersByUserIdApplicationPasswordsByUuid 3 params → 200404400401
POST
/wp/v2/users/{user_id}/application-passwords/{uuid}
POST /wp/v2/users/{userid}/application-passwords/{uuid}
createUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401403404
PUT
/wp/v2/users/{user_id}/application-passwords/{uuid}
PUT /wp/v2/users/{userid}/application-passwords/{uuid}
updateUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401403404
PATCH
/wp/v2/users/{user_id}/application-passwords/{uuid}
PATCH /wp/v2/users/{userid}/application-passwords/{uuid}
patchUsersByUserIdApplicationPasswordsByUuid 2 params body → 200400401403404
DELETE
/wp/v2/users/{user_id}/application-passwords/{uuid}
DELETE /wp/v2/users/{userid}/application-passwords/{uuid}
deleteUsersByUserIdApplicationPasswordsByUuid 2 params → 200400401403404
GET
/wp/v2/users/{user_id}/application-passwords/introspect
GET /wp/v2/users/{userid}/application-passwords/introspect
getUsersByUserIdApplicationPasswordsIntrospect 2 params → 200404400401
GET
/wp/v2/users/me
GET /wp/v2/users/me
getUsersMe 1 param → 200404400401
POST
/wp/v2/users/me
POST /wp/v2/users/me
createUsersMe body → 200400401403404
PUT
/wp/v2/users/me
PUT /wp/v2/users/me
updateUsersMe body → 200400401403404
PATCH
/wp/v2/users/me
PATCH /wp/v2/users/me
patchUsersMe 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 WpError (3 properties). Each schema is shown below with its type and property counts.

WpError
object
The WordPress REST API error envelope returned on every 4xx/5xx.
3 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vestaron-users-api-openapi.yml Raw ↑

Other APIs Vestaron publishes across the network.

Vestaron MCP Server (WordPress MCP Adapter)
AE Profile APIs.io
Vestaron Comments API
AE Profile APIs.io
Vestaron Discovery API
AE Profile APIs.io
Vestaron Media API
AE Profile APIs.io
Vestaron Pages API
AE Profile APIs.io
Vestaron Posts API
AE Profile APIs.io
Vestaron Search API
AE Profile APIs.io
Vestaron Settings API
AE Profile APIs.io
Vestaron Taxonomy API
AE Profile APIs.io
#User
← Back to V APIs
API Details
ID
vestaron:vestaron-users-api
Base URL
https://vestaron.com/wp-json/wp/v2
Docs
https://vestaron.com/news/
Provider
Vestaron
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=vestaron-users-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/vestaron-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 Vestaron 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.