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

Argilla users API

The users API from Argilla — 4 operation(s) for users.

Argilla users API is one of 15 APIs that Argilla 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 API documentation.

This API exposes 7 operations across 4 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version 2.8.0.

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

7 operations 4 paths 7 schemas 1 DELETE4 GET1 PATCH1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.8.0
Base URL
https://argilla.io
Authentication
API Key, HTTP Bearer
License
Resource Areas
1

Authentication & Security 2

Argilla users API declares 2 security schemes for authenticating requests. An API key is passed in the header as X-Argilla-Api-Key (APIKeyHeader). It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 7

Across 4 paths, the API surfaces 7 operations — 1 DELETE, 4 GET, 1 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.

users 7
GET
/me
Get Current User
get_current_user_me_get → 200400404403409422500
GET
/users/{user_id}
Get User
get_user_users__user_id__get 1 param → 200400404403409422500
DELETE
/users/{user_id}
Delete User
delete_user_users__user_id__delete 1 param → 200400404403409422500
PATCH
/users/{user_id}
Update User
update_user_users__user_id__patch 1 param body → 200400404403409422500
GET
/users
List Users
list_users_users_get → 200400404403409422500
POST
/users
Create User
create_user_users_post body → 201400404403409422500
GET
/users/{user_id}/workspaces
List User Workspaces
list_user_workspaces_users__user_id__workspaces_get 1 param → 200400404403409422500

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are User (8 properties), UserCreate (6 properties), UserUpdate (5 properties), Workspace (4 properties). Each schema is shown below with its type and property counts.

User
object
8 properties 7 required
Users
object
1 property 1 required
UserRole
string
Workspace
object
4 properties 4 required
UserCreate
object
6 properties 3 required
Workspaces
object
1 property 1 required
UserUpdate
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

argilla-users-api-openapi.yml Raw ↑

Other APIs Argilla publishes across the network.

Argilla Authentication API
Argilla datasets API
Argilla fields API
Argilla info API
Argilla jobs API
Argilla metadata properties API
Argilla questions API
Argilla records API
Argilla responses API
Argilla settings API
Argilla suggestions API
Argilla vectors-settings API
Where this information came from

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