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

Britive Users, Service Identities and AI Identities API

Manage Users, Service Identities and AI Identities

Britive Users, Service Identities and AI Identities API is one of 79 APIs that Britive publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Users, Service Identities and AI Identities. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 16 operations across 11 paths, and defines 17 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://{tenantURL}.

16 operations 11 paths 17 schemas 1 DELETE5 GET4 PATCH6 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://demo.britive-app.com/api
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Britive Users, Service Identities and AI Identities API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

Paths & Operations 16

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

Users, Service Identities and AI Identities 16

Manage Users, Service Identities and AI Identities

GET
/api/access/users/{userId}/subordinates
Get user subordinates
getSubordinates 3 params → 200404
PATCH
/api/self
Update current user settings
updateSelf body → 204
POST
/api/users
Create a new user
create body → 200
GET
/api/users
Get a list of all Identities
get_1 8 params → 200
GET
/api/users/by-tag/{tagId}
Get Members of a Tag
getTagMembers 3 params → 200400
POST
/api/users/disabled-statuses
Disable a specified user
disabledStatusesBulk body → 200
DELETE
/api/users/{targetUserId}
Delete a specified user
delete 1 param → 200
GET
/api/users/{targetUserId}
Get details of a specified user
get 1 param → 200
PATCH
/api/users/{targetUserId}
Update user details
update 1 param body → 204
POST
/api/users/{targetUserId}/disabled-statuses
Disable a specified user tag
disabledStatuses 1 param → 200
POST
/api/users/{targetUserId}/enabled-statuses
Enable a specified user tag
enabledStatuses 1 param → 200
PATCH
/api/users/{targetUserId}/resetmfa
Reset user's Multi-factor Authentication (MFA)
adminResetMfaForUser 1 param → 200
POST
/api/users/{targetUserId}/resetpassword
Reset user password
adminResetPassword 1 param body → 200
POST
/api/users/{targetUserId}/tokens
Create a token for a specified identity
tokens_1 1 param body → 200
GET
/api/users/{targetUserId}/tokens
Get token details associated with identity
tokens 2 params → 200
PATCH
/api/users/{targetUserId}/tokens
Update the token expiration days for an existing identity token
tokens_2 1 param body → 200

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are User (29 properties), UserBeanResponse (19 properties), Tenant (13 properties), UserBeanRequest (13 properties). Each schema is shown below with its type and property counts.

Tenant
object
13 properties
UserTag
object
12 properties
AdminRole
object
3 properties
UserView
object
7 properties
CustomUserAttribute
object
4 properties
UserBeanResponse
object
19 properties
UserBeanResult
object
6 properties
AttributeMap
object
Single identity provider attribute mapped to service identity custom attribute
2 properties 2 required
UserBeanRequest
object
13 properties
JsonNodeWrapper
object
1 property
JsonNode
object
TagMembersResponse
object
4 properties
IdentityRelationship
object
4 properties
User
object
29 properties
ApiTokenBean
object
11 properties
IdentityProvider
object
6 properties 2 required
AuditStamp
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

britive-users-service-identities-and-ai-identities-api-openapi.yml Raw ↑

Other APIs Britive publishes across the network.

Britive Secrets Manager API
Britive MCP Server
Britive Access Request Tag Membership API
Britive API Tokens API
Britive Application Environments - Accounts API
Britive Application Environments API
Britive Application Profiles - Advanced Settings API
Britive Application Profiles API
Britive Application Profiles - Permission Constraint Manager API
Britive Application Profiles - Permissions API
Britive Application Profiles - Policies API
Britive Application Profiles - Scopes API
Where this information came from

This is an independent, third-party profile of Britive Users, Service Identities and AI Identities 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.