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

Posit Users API

The Users API from Posit — 5 operation(s) for users.

Posit Users API is one of 33 APIs that Posit 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 8 operations across 5 paths, and defines 11 schemas. It is described by OpenAPI 3.2.0, at version 1.0.1.

Requests are made against a single base URL, /__api__.

8 operations 5 paths 11 schemas 4 GET2 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.1
Base URL
https://connect.example.com/__api__
Authentication
API Key
Terms of Service
Resource Areas
1

Authentication & Security 1

Posit Users API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (apiKey). By default, every request must be authenticated.

  • apiKey — Prefix your API key with Key , e.g. Key ABC123.

Paths & Operations 8

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

Users 8
GET
/v1/user
Get current user details
getCurrentUser → 200400401404500
GET
/v1/users
List or search for user details
getUsers 7 params → 200400401403404500
POST
/v1/users
Create a user from caller-supplied details (SAML, password, PAM, proxied, OAuth2 except with Google)
createPushUser body → 200400401403404409500
PUT
/v1/users
Create a user using details from a remote authentication provider (LDAP, OAuth2 with Google)
createPullUser body → 200400401403404409500
GET
/v1/users/remote
Search for user details from a remote provider
searchRemoteUsers 2 params → 200400401403404500
GET
/v1/users/{guid}
Get user details
getUser 1 param → 200400401404500
PUT
/v1/users/{guid}
Update a user
updateUser 1 param body → 200400401403404409500
POST
/v1/users/{guid}/lock
Lock a user
lockUser 1 param body → 200400401403404500

Schemas 11

The contract defines 11 schemas that model the data the API accepts and returns. The most detailed are UserWithTicket (13 properties), User (12 properties), UserCreatePushInput (9 properties), EditableUser (6 properties). Each schema is shown below with its type and property counts.

LockUserInput
object
The fields that must be specified when locking or unlocking a user.
1 property
UserCreatePushInput
object
The fields that can be specified when creating a user from caller-supplied details.
9 properties
RemoteSearchResults
The remote user search results with paging information.
APIError
object
The error object returned by the API on failure.
3 properties 2 required
Users
The users list with paging information.
User
object
A user object.
12 properties
OffsetPaging
object
Offset-based pagination metadata.
2 properties
UserCreatePullInput
object
The fields that must be specified when creating a user from a remote authentication provider.
1 property
UserWithTicket
object
A user object with a temporary ticket for remote user creation.
13 properties
EditableUser
object
The editable user properties.
6 properties
UserUpdateInput
object
The fields that can be specified when updating a user.
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

posit-users-api-openapi.yml Raw ↑

Other APIs Posit publishes across the network.

Posit API Keys API
Posit Audit Logs API
Posit Bookmarks API
Posit Bootstrap API
Posit Bundles API
Posit Content API
Posit Content Permissions API
Posit Custom Documentation API
Posit Environment Permissions API
Posit Environments API
Posit Examples API
Posit Feature Usage API
Where this information came from

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