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

VAST Data users API

Users who can be authorized to access any data on the cluster via any supported client protocol can be created on a local provider. They are more typically stored on external authorization providers (AD, LDAP and NIS). The users path provides: management of local provider users, querying of external provider users, and S3 access management for both local and external users.

VAST Data users API is one of 126 APIs that VAST Data 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, API documentation, and SDKs.

This API exposes 18 operations across 9 paths, and defines 8 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against the base URL https://{vms-host}/api.

18 operations 9 paths 8 schemas 3 DELETE5 GET6 PATCH4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://{vms-host}/api
Authentication
API Key, HTTP Basic
Resource Areas
1

Authentication & Security 2

VAST Data users API declares 2 security schemes for authenticating requests. An API key is passed in the header as ApiToken (ApiToken). It accepts HTTP basic authentication (basicAuth). By default, every request must be authenticated.

  • ApiToken — Send current valid API token in an Authorization header with format Api-Token .
  • basicAuth — Basic authentication using VMS user name and password

Paths & Operations 18

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

users 18

Users who can be authorized to access any data on the cluster via any supported client protocol can be created on a local provider. They are more typically stored on external auth…

GET
/users/
List Users
users_list 2 params → 200
POST
/users/
Add User to a Local Provider
users_add body → 201
POST
/users/copy/
Copy Users with S3 Keys from one Local Provider to Another
users_copy body → 200400404409
GET
/users/names/
Find User by prefix and domain details
users_names 3 params → 200
DELETE
/users/non_local_keys/
Remove S3 Access Key Pair (Non-Local User)
users_non_local_remove_key body → 204
PATCH
/users/non_local_keys/
Enable or Disable S3 Access Key Pair (Non-Local User)
users_non_local_modify_key body → 204
POST
/users/non_local_keys/
Generate S3 Access Key Pair (Non-Local User)
users_non_local_generate_key body → 200
GET
/users/query/
Query User
users_query 7 params → 200
PATCH
/users/query/
Modify non-Local User
users_query_modify body → 200
PATCH
/users/refresh/
Refresh User
users_refresh body → 200
DELETE
/users/{id}/
Delete Local User
users_delete 1 param → 204
GET
/users/{id}/
Return Local User Details
users_read 1 param → 200
PATCH
/users/{id}/
Modify Local User
users_partial_update 1 param body → 200
DELETE
/users/{id}/access_keys/
Remove S3 Access Key Pair (Local User)
users_remove_key 1 param body → 204
PATCH
/users/{id}/access_keys/
Enable/Disable S3 Access Key Pair (Local User)
users_modify_key 1 param body → 204
POST
/users/{id}/access_keys/
Generate S3 Access Key Pair (Local User)
users_generate_key 1 param body → 200
GET
/users/{id}/tenant_data/
Get tenant data for a User
users_get_tenant_data 2 params → 200
PATCH
/users/{id}/tenant_data/
Update Tenant Data for a User
users_update_tenant_data 1 param body → 200

Schemas 8

The contract defines 8 schemas that model the data the API accepts and returns. The most detailed are UserQueryData (27 properties), User (26 properties), UserTenantData (5 properties), PartialS3PolicyInfo (2 properties). Each schema is shown below with its type and property counts.

LocalProviderData
object
2 properties
UserData
object
UserKeyPair
object
2 properties
User
object
26 properties 1 required
UserQueryData
object
27 properties
UserTenantData
object
5 properties
PartialS3PolicyInfo
object
2 properties
AsyncTaskInResponse
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

vastdata-users-api-openapi.yml Raw ↑

Other APIs VAST Data publishes across the network.

VAST Data activedirectory API
VAST Data alarms API
VAST Data apitokens API
VAST Data basicsettings API
VAST Data bgpconfigs API
VAST Data Blob Expansions API
VAST Data Block Hosts API
VAST Data blockhosts API
VAST Data blockmappings API
VAST Data callhomeconfigs API
VAST Data capacity API
VAST Data carriers API
Where this information came from

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