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 Evidence Library API

Drata's Evidence Library serves as a repository for all the evidence you need to collect across your controls. The [help docs](https://help.drata.com/en/articles/8288579-evidence-library-overview) have more information. Note: these are the legacy single-artifact endpoints; new integrations should use the Evidence endpoints.

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

Tagged areas include Evidence Library. 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 6 operations across 3 paths, and defines 19 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.

6 operations 3 paths 19 schemas 1 DELETE3 GET1 POST1 PUT

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 Evidence Library API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API_KEY) (bearer).

Paths & Operations 6

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

Evidence Library 6

Drata's Evidence Library serves as a repository for all the evidence you need to collect across your controls. The [help docs](https://help.drata.com/en/articles/8288579-evidence-…

GET
/workspaces/{workspaceId}/evidence-library
List Evidence Library Items
EvidenceLibraryPublicV2Controller_listEvidenceLibrary 9 params → 200401403404412500
POST
/workspaces/{workspaceId}/evidence-library
Create Evidence Library Item
EvidenceLibraryPublicV2Controller_createEvidenceLibrary 1 param body → 201401403404412500
GET
/workspaces/{workspaceId}/evidence-library/{evidenceLibraryId}
Get Evidence Library Item
EvidenceLibraryPublicV2Controller_getEvidenceLibrary 3 params → 200401403404412500
PUT
/workspaces/{workspaceId}/evidence-library/{evidenceLibraryId}
Update Evidence Library Item
EvidenceLibraryPublicV2Controller_updateEvidenceLibrary 2 params body → 200401403404412500
DELETE
/workspaces/{workspaceId}/evidence-library/{evidenceLibraryId}
Delete Evidence Library Item
EvidenceLibraryPublicV2Controller_deleteEvidenceLibrary 2 params → 204401403404412500
GET
/workspaces/{workspaceId}/evidence-library/{evidenceLibraryId}/versions/{versionId}
Get Evidence Library Version
EvidenceLibraryPublicV2Controller_getEvidenceLibraryVersion 4 params → 200401403404412500

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are EvidenceLibraryCreateRequestPublicV2Dto (13 properties), EvidenceLibraryModifyRequestPublicV2Dto (12 properties), EvidenceLibraryCompactResponsePublicV2Dto (11 properties), EvidenceLibraryVersionResponsePublicV2Dto (8 properties). Each schema is shown below with its type and property counts.

EvidenceLibraryModifyRequestPublicV2Dto
object
12 properties
EvidenceLibraryExpandEnum
string
ControlCompactResponsePublicV2Dto
object
7 properties 6 required
ExceptionResponseDto
object
4 properties 3 required
EvidenceLibraryVersionCompactResponsePublicV2Dto
object
5 properties 5 required
RenewalSchemaCompactResponsePublicV2Dto
object
3 properties 3 required
UserCompactResponsePublicV2Dto
object
6 properties 6 required
SortDirectionEnum
string
EvidenceStatusEnum
string
EvidenceLibraryCreateRequestPublicV2Dto
object
13 properties 1 required
EvidenceLibraryListResponsePublicV2Dto
object
2 properties 2 required
RenewalScheduleTypeEnum
string
ExceptionResponsePublicV2Dto
object
5 properties 4 required
PaginationTotalCountResponsePublicV2Dto
object
2 properties 1 required
LibraryDocumentVersionTypeEnum
string
EvidenceLibraryVersionExpandEnum
string
EvidenceLibraryCompactResponsePublicV2Dto
object
11 properties 7 required
SortTypeLimitedEnum
string
EvidenceLibraryVersionResponsePublicV2Dto
object
8 properties 7 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

drata-evidence-library-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 Evidence Library 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.