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

Pynt User API

The user API from Pynt — 3 operation(s) for user.

Pynt User API is one of 32 APIs that Pynt 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, an API reference, and API documentation.

This API exposes 5 operations across 3 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://api.pynt.io.

5 operations 3 paths 6 schemas 1 DELETE2 GET1 PATCH1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.pynt.io
Authentication
API Key, API Key, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 5

Pynt User API declares 5 security schemes for authenticating requests. An API key is passed in the header as X-API-Key (API_Key). An API key is passed in the header as Authorization (Bearer_Token). An API key is passed in the header as X-System-API-Key (System_API_Key). An API key is passed in the header as X-Organization-ID (Organization_ID). An API key is passed in the header as context (Operator_Organization_Context).

Paths & Operations 5

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

user 5
GET
/v1/user/me
Get User Me
get_user_me_v1_user_me_get → 200
GET
/v1/user
List Users
list_users_v1_user_get 1 param → 200422
PUT
/v1/user
Create User
create_user_v1_user_put → 200
PATCH
/v1/user/{user_id}
Update User By Id
update_user_by_id_v1_user__user_id__patch 1 param body → 200422
DELETE
/v1/user/{user_id}
Delete User By Id
delete_user_by_id_v1_user__user_id__delete 1 param → 200422

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are UserOut (10 properties), ValidationError (3 properties), UserUpdateModel (1 property), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

UserOut
object
10 properties 10 required
UserRole
string
CreateUserResponse
object
1 property 1 required
HTTPValidationError
object
1 property
ValidationError
object
3 properties 3 required
UserUpdateModel
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pynt-user-api-openapi.yml Raw ↑

Other APIs Pynt publishes across the network.

Pynt Alive API
Pynt API Key API
Pynt Application API
Pynt Artifacts API
Pynt Auth API
Pynt Aws Marketplace API
Pynt Config API
Pynt Endpoint Group API
Pynt Endpoint Llm Analysis API
Pynt Event Logs API
Pynt Evidence API
Pynt Integrations API
Where this information came from

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