Drata

Drata Custom Data Records API

Custom Data Records are JSON evidence records pushed to a Custom Connection resource. Use the session management endpoints to batch upload records and track the status of bulk operations. You can create monitors on this data to provide continuous compliance. The [help docs](https://help.drata.com/en/articles/11995676-part-1-custom-connections-and-tests) have more information.

GitHub OpenAPI

Operations 7

Each operation below carries the questions people ask an LLM about it and the instructions they give an agent to run it. Generated by API Evangelist overlay

GET /custom-connections/{connectionId}/resources/{resourceId}/records List records for a custom connection resource · List Custom Data Records #
Ask an LLM
“What data records have we pushed to a custom connection?”
“Can I list only the records uploaded in one session?”
Tell an agent
List records for resource {resource} on custom connection {connection}.
Show records from session {session} for resource {resource} on connection {connection}.
POST /custom-connections/{connectionId}/resources/{resourceId}/records Upsert custom data records · Upsert Custom Data Records #
Ask an LLM
“How do I push my own data into a custom connection?”
“Does sending a record create it or update the existing one?”
Tell an agent
Upsert records {data} into resource {resource} of custom connection {connection}.
Send these records {data} to connection {connection}, resource {resource}.
GET /custom-connections/{connectionId}/resources/{resourceId}/sessions List upload sessions for a resource · List Custom Data Sessions #
Ask an LLM
“Which batch upload sessions exist for a custom resource?”
“Can I filter custom data sessions by status?”
Tell an agent
List upload sessions for resource {resource} on connection {connection}.
Show sessions with status {status} for resource {resource} on connection {connection}.
POST /custom-connections/{connectionId}/resources/{resourceId}/sessions/{sessionId} Upload a batch of records in a session · Upsert Custom Data Records with Session Management #
Ask an LLM
“Can I upload custom data in batches inside a session?”
“How do I add more records to an open upload session?”
Tell an agent
Upload batch {data} to session {session} for resource {resource} on connection {connection}.
Add records {data} to open session {session}.
POST /custom-connections/{connectionId}/resources/{resourceId}/sessions/{sessionId}/actions Act on a custom data upload session · Perform Session Action #
Ask an LLM
“How do I finish or close a custom data upload session?”
“What actions can I take on an upload session?”
Tell an agent
Perform action {action} on session {session} for resource {resource} on connection {connection}.
Apply {action} to upload session {session}.
PUT /custom-connections/{connectionId}/resources/{resourceId}/records/{recordId} Update one custom data record · Update Custom Data Record #
Ask an LLM
“Can I update a single custom data record by its ID?”
“Is it possible to correct one record without re-uploading everything?”
Tell an agent
Update record {record} in resource {resource} on connection {connection} with {data}.
Replace the data of record {record} with {data}.
DELETE /custom-connections/{connectionId}/resources/{resourceId}/records/{recordId} Delete one custom data record · Delete Custom Connection Data Record #
Ask an LLM
“Can I delete a single record from a custom connection?”
“Is removing a custom data record permanent?”
Tell an agent destructive · confirm first
Delete record {record} from resource {resource} on connection {connection}.
Remove custom data record {record}.

Documentation

📖
Documentation
https://developers.drata.com/openapi/reference/v2/overview/
📖
APIReference
https://developers.drata.com/openapi/reference/v2/overview/
📖
GettingStarted
https://developers.drata.com/developer-portal/v2/recipes/create-an-api-key/
📖
Authentication
https://artifacts.apis.io/drata/authentication/drata-authentication.yml
📖
Documentation
https://developers.drata.com/openapi/reference/v2/tag/Custom-Connections/
📖
GettingStarted
https://developers.drata.com/developer-portal/v2/recipes/custom-connections/
📖
Documentation
https://docs.safebase.io/reference/getaccounts
📖
APIReference
https://docs.safebase.io/reference/getaccounts

Specifications

⚙
OpenAPI
https://artifacts.apis.io/drata/openapi/drata-custom-data-records-api-openapi.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/drata:drata-custom-data-records-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

drata-custom-data-records-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Drata Custom Data Records API
  description: '### What''s New in V2

    - Support for Custom Fields

    - Get and acknowledge user''s assigned policies

    - Payloads are streamlined to include only the essential information. You can expand related objects and collections using the `expand` query parameter.

    - Cursor-based pagination for greater efficiency and stability with large datasets


    ### Getting Started

    Please visit our help article to learn how to create an API key.


    ### Upgrading From Version 1

    API V2 is designed to provide a faster an more flexible way of accessing Drata. There are several differences from V1:

    - The listing endpoints now use **cursor-based pagination**. This provides faster responses and ensures that all records can be retrieved even, if they are changed during the process.


    ```javascript

    async function fetchAll() {

    // The first request doesn''t send a value for the cursor.

    let cursor = undefined;

    do {

    const query = new URLSearchParams({ cursor });

    const resp = await fetch(

    `https://public-api.drata.com/public/v2/users?${query}`,

    {

    method: ''GET'',

    headers: { Authorization: ''Bearer '' }

    }

    );

    const data = await resp.json();

    console.log(data);


    // If there''s a cursor value returned, then there are more results.

    // Pass that back as a query parameter to get the next page of data.

    cursor = data?.pagination?.cursor;

    } while (cursor)

    }

    fetchAll();

    ```

    - You''ll notice smaller responses. Most endpoints accept an `expand` query parameter that let''s you specify which related objects and collections you want to expand.'
  version: V2
  contact: {}
servers:
- url: https://public-api.drata.com/public/v2
- url: https://public-api.eu.drata.com/public/v2
- url: https://public-api.apac.drata.com/public/v2
tags:


# --- truncated at 32 KB (43 KB total) ---
# Full source: https://artifacts.apis.io/drata/openapi/drata-custom-data-records-api-openapi.yml