RelativityOne Developer News

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.

The Analytics Classification API (.NET and REST) was removed from RelativityOne on December 20, 2024. See this post in the developer group for more information.

The Object Manager REST API returns a 554 status code if an event handler causes Object Manager's REST API to fail. The 554 error will help you troubleshoot when operations fail due to an issue with event handlers. See this post in the developer group for more information.

The DataExchange.Client.SDK is deprecated in RelativityOne as of December 2, 2024. The Relativity.Import.SDK replaces the DataExchange.Client.SDK. See this post in the developer group for more information.

The Solution Snapshot application will no longer be supported for Relativity Server as of October 29, 2024. All supporting documentation and access to the RAP will be removed at that time, and no further changes will be made to the application. See this post in the developer group for more information.

RelativityOne Staging boundaries are streamlined to effectively separate staging data from workspace and system data. With this change, you will no longer be able to write to or access data outside of the defined staging area. The FTA, Temp, Export and dtSearch folders will be removed. For more detail, please reference the Staging Area FAQ community article.

The Relativity Testing Framework (RTF) for RelativityOne is no longer available as of May 31, 2024.  All supporting documentation and access to the NuGet package has been removed and no further changes will be made to the application. Developers should move to using the Relativity APIs directly as a better, truer indication of test. See this post in the developer group for more information.

RTF will continue to be supported for Relativity Server. Effective with the Server 2023 release you can find the latest RTF SDK package on the Server SDK package feed here. For more information on the Server SDK feed and go-forward Server SDK strategy please see this topic.

The API Explorer application is no longer supported for RelativityOne nor Relativity Server as of May 20, 2024. All supporting documentation and access to the RAP file has been removed, and no further changes will be made to the application. See this post in the developer group for more information.

Object Manager consumers on a per-application basis will no longer be able to exceed 1,000 requests per minute per Web Server. Upon reaching this limit, Object Manager will respond with an exception (429 - Too many Requests) and will reject the request. This change was applied to Sandboxes on December 20th, 2023 and in Production environments on March 20th, 2024. See the topic Rate limit for best practices and code samples to cater for the rate limiting feature, and see this post in the developer group for more information.

Relativity.Transfer.Client versions 7.4.10 and below stopped functioning on January 31, 2024, due to the migration of Relativity data transfer products to cloud-based solutions. If your code contains a reference to Relativity.Transfer.Client, you will need to update your code to integrate with Relativity.Transfer.SDK, version 1.0.0+. See this post in the developer group for more information.

The Send to CaseMap mass operation is being deprecated in RelativityOne and will be removed around November 28, 2023. If you bulk-send items to your CaseMap database (versions 7 and above) using the mass operation and require similar functionality in RelativityOne, our Case Dynamics product offers similar capabilities. See this post in the developer group for more information.

This developer documentation site has been significantly updated to better support Relativity developers. Some noteworthy improvements include:

• Re-organization of content into three main categories: Explore, Integrate and Extend to more closely align with how you may need to interact with our developer documentation.
• Added hyperlinks to headings within topics, allowing you to easily copy a hyperlink to a heading within a topic. Mouse-over any heading to display the link image and then click the link image to copy a hyperlink to that heading.
• Added a topic contents listing on the right-hand side of topics, allowing you to easily see the sections within a topic and quickly jump to the relevant section in that topic. See Basic REST API concepts as an example.
• Implemented a new approach for displaying reference documentation for .NET assembles, based on real-time retrieval from NuGet. See the topic Relativity Identity .NET API Reference as an example.
• Implemented a new approach for displaying reference documentation for REST services, based on OpenAPI (OAS) files. See the topic Billing Insights REST API Reference as an example. You can also download OAS files for Rest services to use these in your own development tooling.
• Improved the API listing table to include links to reference documentation, NuGet packages and OAS files where available. The table is also now filterable and sortable.

The unversioned Production APIs will be deprecated and no longer supported as of July 28, 2023. If your .NET code contains a reference to Relativity.Productions.Client or you are calling the non-versioned Production service URLs, you will need to update your code to use Relativity.Productions.SDK or alternatively target the versioned REST service URLs. See this post in the developer group for more information.

The unversioned Audit API will be deprecated in June 2023. If your .Net code contains a reference to Relativity.Audit.Services.Unversioned.Interfaces or you are calling the non-versioned service URL, you will need to update your code. See this post in the developer group for more information.