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

Drata HRIS User Identities API

HR user identity records for a Custom HRIS connection. Use the batch upsert endpoint to submit employee records keyed by your own `identityId`, then use the update endpoint to reflect employment changes (e.g. set `separatedAt` when an employee leaves). Deleting a record is intended for data submitted in error, not for offboarding. Changes are not applied immediately — they are incorporated the next time identity sync runs, which happens nightly by default. A sync can also be triggered manually from the Personnel page.

Drata HRIS User Identities API is one of 52 APIs that Drata publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include HRIS User Identities. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

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

Requests are made against 3 base URLs: https://public-api.drata.com/public/v2, https://public-api.eu.drata.com/public/v2, https://public-api.apac.drata.com/public/v2.

4 operations 2 paths 9 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
V2
Base URL
https://public-api.drata.com/public/v2
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Drata HRIS User Identities API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API_KEY) (bearer).

Paths & Operations 4

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

HRIS User Identities 4

HR user identity records for a Custom HRIS connection. Use the batch upsert endpoint to submit employee records keyed by your own identityId, then use the update endpoint to refle…

GET
/custom-connections/{connectionId}/hris-user-identities
List HRIS User Identities 🧪
CustomHrisUserIdentitiesPublicV2Controller_listCustomHrisUserIdentities 6 params → 200401402403404412500
POST
/custom-connections/{connectionId}/hris-user-identities
Create or Update HRIS User Identities 🧪
CustomHrisUserIdentitiesPublicV2Controller_createCustomHrisUserIdentities 1 param body → 200201207400401402403404
GET
/custom-connections/{connectionId}/hris-user-identities/{userIdentityId}
Get HRIS User Identity 🧪
CustomHrisUserIdentitiesPublicV2Controller_getCustomHrisUserIdentity 2 params → 200400401402403404412500
DELETE
/custom-connections/{connectionId}/hris-user-identities/{userIdentityId}
Delete HRIS User Identity 🧪
CustomHrisUserIdentitiesPublicV2Controller_deleteCustomHrisUserIdentity 2 params → 204400401402403404412500

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are CustomUserIdentityResponsePublicV2Dto (14 properties), CustomUserIdentityRecordPublicV2Dto (11 properties), ExceptionResponsePublicV2Dto (5 properties), ExceptionResponseDto (4 properties). Each schema is shown below with its type and property counts.

ExceptionResponsePublicV2Dto
object
5 properties 4 required
PaginationTotalCountResponsePublicV2Dto
object
2 properties 1 required
CustomUserIdentitiesResponsePublicV2Dto
object
2 properties 2 required
SortTypeLimitedEnum
string
CustomUserIdentityBulkResponsePublicV2Dto
object
3 properties 2 required
ExceptionResponseDto
object
4 properties 3 required
CustomUserIdentityRecordPublicV2Dto
object
11 properties 1 required
CustomUserIdentityResponsePublicV2Dto
object
14 properties 14 required
SortDirectionEnum
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

drata-hris-user-identities-api-openapi.yml Raw ↑

Other APIs Drata publishes across the network.

Drata MCP Server
Drata Account Members API
Drata Accounts API
Drata Assets API
Drata Audit Requests API
Drata Audits API
Drata Background Checks API
Drata Company API
Drata Control Library API
Drata Control Notes API
Drata Control Owners API
Drata Controls API
Where this information came from

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