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

Scimar Users API

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

Scimar Users API is one of 10 APIs that Scimar 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 wp/v2.

Requests are made against a single base URL, https://scimar.ca/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://scimar.ca/wp-json
Authentication
HTTP Basic
Contact
Resource Areas
1

Authentication & Security 1

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

  • applicationPassword — WordPress Application Passwords (HTTP Basic). The scimar.ca WordPress install registers the application-passwords routes at /wp/v2/users/{userid}/application-p…

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 → 200400401403404
POST
/wp/v2/users
POST /wp/v2/users
createUsers body → 200400401403404
GET
/wp/v2/users/{id}
GET /wp/v2/users/{id}
getUsersById 2 params → 200400401403404
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 → 200400401403404
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 → 200400401403404
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 → 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
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 (WPError serialized to JSON).
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

scimar-users-api-openapi.yml Raw ↑

Other APIs Scimar publishes across the network.

Scimar MCP Server (WordPress MCP Adapter)
Scimar Comments API
Scimar Discovery API
Scimar Media API
Scimar Pages API
Scimar Posts API
Scimar Search API
Scimar Settings API
Scimar Taxonomy API
Where this information came from

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