The DISCO API provides direct communication between DISCO Ediscovery and your organization’s business intelligence solution, making it easier to see the big picture and take action on data from across your organization. With access to detailed information, you may estimate or reconcile an invoice, audit anomalies or discrepancies in your organization’s data usage, or manage data usage against a subscription cap or monthly budget. For clients who run their financial or operational analysis by aggregating data from different sources, this read-only API will enable simplified, on-demand access to DISCO Ediscovery data.

Each request requires a DISCO issued API Key and includes CIDR block verification. Organization managers have access to the API functionality via the Settings tab, where they can add or remove IPv4 CIDR formatted trusted sources which serve as the specific IP addresses permitted to access the API. Authorized users can also be managed in the Settings tab. An API key can be created to grant access to the API for those users first at the organization level, and secondarily at the per-authorized user level. Users must submit their API Key with each request.

The total of all API requests to all endpoints is limited to 100 per minute per customer organization.

All URIs listed below begin after the DNS domain name (e.g. https://api.csdisco.com). Due to the highly sensitive nature of our industry, all requests for a specific resource that would include some identifier will use POST methods and include the parameter in the body of the request.

URL paths and resource names are case-sensitive, e.g. /datasets/data-usage-changes, but the DNS name is case-insensitive, e.g. https://api.csdisco.com/. HTTP header parameters are case-insensitive, e.g. disco-api-key. Body parameter names are case-sensitive, e.g. start-date.

The header keys disco-api-key and organization-id must be provided by the user on every call. cURL Example

   curl --header "disco-api-key: 1234-6789/12" --header "organization-id: 01234567" https://api.csdisco.com/datasets/data-usage-changes/metadata

All payloads should come in standard key/value format for all headers, and JSON format for POST body content.

We will follow the major/minor/patch pattern for versioning.

All API calls return HTTP status 200 for success, or status 4xx which typically means an error by the client in forming the query, or status 5xx which means an internal error occurred.

The endpoints listed below are arranged into 3 different types - Datasets, Metrics, and Metadata. Dataset endpoints contain collections of raw data pertaining to a specific topic, such as data-usage change events over time. Metric endpoints are singular aggregated calculations within a raw dataset, such as reviewdb size at a specific time. Metadata endpoints present either the metadata fields of a particular dataset for example or provide lists of datasets or metrics available to be utilized. The following datatypes may appear in metadata:

  Integer: currently not specified as 32-bit vs. 64-bit
  string: UTF-8
  timestamp: ISO-8601 format with timezone offset, e.g. "2023-01-01T00:00:00.000-05:00"