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

TrustArc Users API

The Users API from TrustArc — 34 operation(s) for users.

TrustArc Users API is one of 56 APIs that TrustArc 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 authentication docs.

This API exposes 41 operations across 34 paths, and defines 32 schemas. It is described by OpenAPI 3.2.0, at version v1.

Requests are made against a single base URL, https://login.truste.com.

41 operations 34 paths 32 schemas 4 DELETE16 GET1 PATCH17 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
v1
Base URL
https://login.truste.com
Authentication
OAuth 2.0
Resource Areas
1

Authentication & Security 1

TrustArc Users API declares 1 security scheme for authenticating requests. It supports OAuth 2.0 (guardianAuth) using the implicit flow, exposing 1 scope.

Paths & Operations 41

Across 34 paths, the API surfaces 41 operations — 4 DELETE, 16 GET, 1 PATCH, 17 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Users 41
GET
/external/api/v2/scim/Users/{id}
getUser 2 params → 200
PUT
/external/api/v2/scim/Users/{id}
updateUser 2 params body → 200
DELETE
/external/api/v2/scim/Users/{id}
deleteUser 1 param → 204
PATCH
/external/api/v2/scim/Users/{id}
patchUser 2 params body → 200
GET
/api/v1/users/{id}
get_4 5 params → 200
PUT
/api/v1/users/{id}
update_2 2 params body → 200
DELETE
/api/v1/users/{id}
delete_2 1 param → 204
PUT
/api/v1/users/{id}/nymity
updateNymityId 2 params → 204
GET
/external/api/v2/scim/Users
getUsers 4 params → 200
POST
/external/api/v2/scim/Users
createUser body → 201
POST
/external/api/v1/users
upsert_1 1 param body → 200
POST
/external/api/v1/users/batch
upsertAll 1 param body → 200
GET
/api/v1/users
list_2 22 params → 200
POST
/api/v1/users
create_2 2 params body → 200
POST
/api/v1/users/{id}/unmanagepassword
unmanagePassword 1 param → 200
POST
/api/v1/users/{id}/unlockpassword
unlockPassword 1 param → 200
POST
/api/v1/users/{id}/totp/reset
resetTotp 1 param → 200
POST
/api/v1/users/{id}/totp/enable
enableTotp 1 param → 200
POST
/api/v1/users/{id}/totp/disable
disableTotp 1 param → 200
POST
/api/v1/users/{id}/resetpassword
resetPassword_1 2 params → 200
POST
/api/v1/users/{id}/enable
enable 1 param → 200
POST
/api/v1/users/{id}/disable
disable 1 param → 200
POST
/api/v1/users/{id}/confirmcredentials
confirmCredentials 1 param → 200
POST
/api/v1/users/search/refresh
searchRefresh 1 param → 204
POST
/api/v1/users/enable
enableAllIn 1 param → 200
POST
/api/v1/users/disable
disableAllIn 1 param → 200
POST
/api/v1/users/confirmcredentials
confirmCredsAllIn 1 param → 200
GET
/external/api/v1/users/externalIds
getByExternalIds 6 params → 200
GET
/external/api/v1/users/externalId
getByExternalId 6 params → 200
GET
/api/v1/users/username_account
getByUserNameAndAccountId 6 params → 200
GET
/api/v1/users/username/{username}
getByUserName 5 params → 200
GET
/api/v1/users/search
search 13 params → 200
GET
/api/v1/users/nymity/{nymityId}
getByNymityId 5 params → 200
GET
/api/v1/users/listoffset
listOffset 11 params → 200
GET
/api/v1/users/list
list_14 21 params → 200
GET
/api/v1/users/ids
getUserByIds 6 params → 200
GET
/api/v1/users/externalIds
getByExternalIds_1 5 params → 200
GET
/api/v1/users/externalId
getByExternalId_1 5 params → 200
GET
/api/v1/users/count
count 14 params → 200
DELETE
/external/api/v1/users/usernames
deleteAll 1 param → 204
DELETE
/external/api/v1/users/username/{username}
delete_19 1 param → 204

Schemas 32

The contract defines 32 schemas that model the data the API accepts and returns. The most detailed are UserCredentials (26 properties), ScimUserResource (25 properties), JsonNode (24 properties), PageUserCredentials (11 properties). Each schema is shown below with its type and property counts.

Meta
object
7 properties
RemoveOperation
1 required
PageUserCredentials
object
11 properties
ReplaceOperation
UserMetaTag
object
4 properties
UserExtensionDTO
object
4 properties
SortObject
object
3 properties
PhoneNumber
object
4 properties
ScimUserResource
object
25 properties
PageableObject
object
6 properties
X509Certificate
object
4 properties
PermissionProfileUserGroup
object
3 properties
Role
object
4 properties
ScimUserName
object
2 properties
BatchUpsertResult
object
3 properties
UserCredentials
object
26 properties
PatchRequest
object
5 properties 1 required
PermissionProfile
object
10 properties
ScimGroup
object
4 properties
InstantMessagingAddress
object
4 properties
Address
object
8 properties
PatchOperation
object
3 properties 1 required
Entitlement
object
4 properties
JsonNode
object
24 properties
Email
object
4 properties
ClientApplicationRole
object
5 properties
AddOperation
Photo
object
4 properties
ErrorList
object
2 properties
SliceUserCredentials
object
9 properties
ListResponseScimUserResource
object
5 properties 1 required
UserGroup
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

trustarc-users-api-openapi.yml Raw ↑

Other APIs TrustArc publishes across the network.

TrustArc Cookie Consent Manager External API
TrustArc Individual Rights Manager External API
TrustArc Consent & Preference Manager External API
TrustArc Data Mapping Hub External Integration API
TrustArc Cookie Consent Manager Reporting API
TrustArc Assessment Manager API
TrustArc Accounts API
TrustArc Accounts Custom Meta Tags API
TrustArc Accounts Extension API
TrustArc Accounts Fieldtypes API
TrustArc Accounts Meta Tags API
TrustArc Accounts Organizational Structure API
Where this information came from

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