RelativityOne Developer News

The Object Manager StreamLongText endpoint in RelativityOne is rate-limited. See this post in the developer group for more information.

All Transfer SDK versions earlier than version 4.2.2 are removed and will no longer function. You need to update references to earlier SDK versions to use the latest version instead. See this post in the developer group for more information.

Several Workspace Manager API endpoints are deprecated as part of an effort to modernize and simplify the Relativity API surface. See this post in the developer group for more information.

Static filter endpoints in the Processing API (CreateExpressionFilterAsync, GetFiltersAsync, GetFiltersByDataSourceAsync, UpdateExpressionFilterAsync, DeleteFilterAsync, GetFilterResultAsync) are deprecated. See this post in the developer group for more information.

v0 versions of Processing APIs no longer function and you will need to use v1/v2 versions of Processing APIs instead. See this post in the developer group for more information.

After June 2026 the legacy Document Viewer Kepler/.NET API Endpoints are deprecated and replaced with new REST API endpoints. See this post in the developer group for more information.

Two Cold Storage API endpoints (CanManageColdStorageAsync and DeleteWorkspaceFromColdStorageAsync) are removed as part of ongoing platform cleanup and modernization actions. See this post in the developer group for more information.

As of July 2026, V1 versions of ARM API endpoints no longer function and you need to use V3 versions of ARM API endpoints instead. See this post in the developer group for more information.

Custom Triggers in Relativity SQL databases (TRIGGER) should no longer be used. See this post in the developer group for more information.

Direct access to Processing SQL DataStores (e.g.: INVXXXXXXX) has been removed. If you do not utilize direct SQL access in your Processing workflows no action is required. If you do utilize direct SQL access in your Processing workflows, you will need to migrate your workflows to API-based ones. See this post in the developer group for more information.

The new get-nisted-documents endpoint in the ProcessingFilterManager API provides the ability to report on specific files excluded from Discovery via DeNIST filtering. See Download NISTed documents list for a processing set for more information.

We now provide both llms.txt files and MCP endpoints for published RelativityOne documentation, which you can use to build your own generative and agentic AI assistance solutions.

• RelativityOne User Guide: llms.txt, mcp-index.json
• RelativityOne Developer Documentation: llms.txt, mcp-index.json

The Staging Reports v3 API is deprecated and replaced with v4, which provides better performance and uses new technology to support functionality for future features. See this post in the developer group for more information.

The ProcessingFilterManager and ProcessingDocumentManager V1 APIs are deprecated and removed in favor of V2 APIs that utilize the LogicalID field instead of the FileID field in its operations. This change impacts operations in ProcessingFilterManager and ProcessingDocumentManager that utilize or return FileID. Code or workflows that utilize these .NET APIs or REST endpoints will need to be ported to the new V2 APIs. See this post in the developer group for more information.

OAuth2 clients will only display the client secret once: immediately after creation. You must copy and securely store it immediately to use in your application's code. The secret will be hidden from all users after the initial page view. If you need to retrieve a client secret after it has been hidden, you will need to reset (generate a new) OAuth2 client secret.

As of August 29, 2025 legacy load file workflows, both import and export, are not supported in Integration Points. If you do not use Integration Points API to import or export load files, no action is required on your end. If you do use legacy load file workflows, you will need to use alternate APIs. Import/Export offers similar functionality with additional features such as enhanced field mapping and advanced job status tracking, improved reliability, and a more seamless user experience. As a replacement to Integration Points API, the Transfer API can be used to move data into/from RelativityOne. In addition, Import Service/Export Service APIs can be used for importing or exporting data into/from workspaces. See this post in the developer group for more information.

As previously communicated, Relativity.ListPage has been replaced by Relativity.Lists. Any third-party applications with List Page Interaction event handlers for Relativity.ListPage must be updated to provide equivalent event handlers for Relativity.Lists. See this post in the developer group for more information, as well as the Classic List Page API deprecation reference page.

You can now optionally include the calculated processing duplicate hash (PDH) value when retrieving discovered documents with the GetDiscoveredDocuments endpoint in the Processing Filter Manager API. This addition is primarily to support advanced deduplication workflows, such as building custom deduplication tools.

Both the billing logic and the functionality of moving a workspace to Cold Storage rely exclusively on the system-defined "Workspace State" field. The customer-defined "Status" field will no longer influence workspace behavior or billing. Automations that depend on the "Status" field for the purpose of Cold Storage management may cease to work as a result of this change. See this post in the developer group for more information.

The Collect Folder Path Data solution, which reports the total number and size of document files in each workspace and folder in a Relativity instance, is being deprecated and will be removed starting June 5, 2025. The deprecation includes the application, agents, event handlers, and the script for this solution. See this post in the developer group for more information.

Lucene Search is deprecated in both the Audit UI and API and removed starting June 2, 2025. In its place, we are introducing basic keyword filtering capabilities using the "is like" and "is not like" operators on the Details field. This change affects how users filter audit records and may require adjustments to existing workflows. See this post in the developer group for more information.

The Audit Metrics REST API endpoint that returns Audit Record Count and Audit Record Size (in bytes) is deprecated. After March 16, 2025, queries to this endpoint will return 0. The endpoint will be fully retired on October 1, 2025. See this post in the developer group for more information.

Lucene Search Engine support in the Audit User Interface and Audit API is removed from production RelativityOne instances. After the deprecation, you will no longer be able to use the keyword LuceneSearch in the request.condition or request.rowCondition in the Audit API. See this post in the developer group for more information.