The API Report CardAPI Index
Relativity

Relativity API

relativity.com

Relativity runs a deep developer platform: REST and .NET Kepler APIs at platform.relativity.com with OAuth2, NuGet SDKs, published rate limits, and Developer Program sandboxes. The gap is eventing: there are no universal webhooks, so partners poll the Audit API.

Last verified: July 2026Legal
API GRADE
F
VERIFIED JUL 2026

SCORECARD

ExistenceGOODPublic REST and typed .NET Kepler APIs with versioned docs at platform.relativity.com and NuGet SDKs.
AccessGOODThe Relativity Developer Program grants sandbox access and documentation is open; no partner or sales gate is documented.
CoverageGOODAPIs span objects, search, productions, processing, import and export, audit, legal hold, and user management.
AuthGOODOAuth2 bearer tokens issued by the OAuth2 Client Manager, with basic and cookie auth as documented fallbacks.
Docs & DXGOODPortal at platform.relativity.com, NuGet SDKs, GitHub samples, Developer Program sandbox, and certification tracks.
StabilityMIXEDRate limits and versioned docs are published, but artifact IDs change on ARM or clone, breaking integrations that hardcode them.
Supergood: Relativity has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Relativity scores F on the API Report Card. Relativity runs a deep developer platform: REST and .NET Kepler APIs at platform.relativity.com with OAuth2, NuGet SDKs, published rate limits, and Developer Program sandboxes. The gap is eventing: there are no universal webhooks, so partners poll the Audit API.

Tried to integrate with Relativity?
SOURCES
Kepler / .NET-first SDKs make non-.NET partner integrations (Node/Python/Go) heavier, REST clients work but require manually building DTOs from the .NET model platform.relativity.com β†—
OAuth2 token lifecycle (issuance, rotation, per-workspace scope) is non-trivial; many partners default to basic auth in dev and hit prod gaps later platform.relativity.com β†—
Rate limits and throttling on multi-tenant RelativityOne are per-action and opaque; bulk Object Manager and Import API jobs frequently throttle without clear retry guidance platform.relativity.com β†—
Import API throughput limits force partners to chunk uploads and tune batch sizes carefully; legacy WinEDDS / Relativity Desktop Client load-file path was deprecated in favor of Import API and Staging Reports API platform.relativity.com β†—
Audit API is the de facto event stream because there is no first-class webhook system for most events; partners poll Audit at risk of missing high-velocity events platform.relativity.com β†—
Workspace artifact IDs change on ARM/clone, partner integrations that hardcode IDs break on workspace mobility and template promotion platform.relativity.com β†—
Versioning sprawl across RelativityOne (continuously rolling) vs Relativity Server 2024 and Server 2025 vs legacy 10.3/9.x means partners must matrix-test multiple SDK versions platform.relativity.com β†—
FedRAMP / Government tenant isolation requires separate OAuth credentials and a separate Kepler endpoint per environment, partners often miss this in onboarding platform.relativity.com β†—
Custom event handlers and agents must be deployed as signed .NET assemblies and run inside the customer's tenant, there is no serverless/edge equivalent for non-.NET partners platform.relativity.com β†—
Integration Points connector framework is .NET-only and historically under-documented for custom source/destination providers platform.relativity.com β†—
Large transfers via Transfer SDK require careful tuning of UDP/Aspera-style parameters; default settings often underperform platform.relativity.com β†—
AI / aiR APIs are newer, partially documented, and per-document/per-token billing is hard to forecast or pre-flight relativity.com β†—
Webhook gap: no native HTTP push for object change, batch completion, production export complete, or aiR completion, partners must hand-roll polling or Automated Workflow callouts platform.relativity.com β†—
OAuth2 Client Manager UI/UX for creating, rotating and scoping credentials is admin-heavy and not self-serve for downstream partner orgs platform.relativity.com β†—
Total cost of ownership for RelativityOne is high, independent reviews estimate 3-year TCO around $450K, materially above Everlaw, Casepoint and Logikcull veniosystems.com β†—
Pricing is quote-driven, with at least 4 documented hidden costs (implementation, training, processing/hosting overages, add-on AI/Trace/Contracts SKUs); median small customer pays ~$800/year, with enterprise contracts reaching $25K/month costbench.com β†—
Reviewers report slow loading times during large document uploads and bulk operations; performance degrades as document counts cross several million capterra.com β†—
RelativityOne outages do happen; when the multi-tenant platform goes down, customers must wait for centralized restoration with limited self-service remediation capterra.com β†—
Steep learning curve, admins typically need certification (RCA, RCU, RCS) and end-users need formal training to be productive softwareadvice.com β†—
Legacy Relativity Server installations require .NET, IIS and SQL Server expertise; multi-server topologies are painful to upgrade and patch gartner.com β†—
Some partner integrations broke during the Relativity Trace product rationalization and sunset of certain compliance-surveillance features relativity.com β†—
Customers cite invoice opacity for processing GB and hosted GB tiers, and difficulty forecasting AI consumption (aiR per-document/per-token charges) gartner.com β†—
Customers in regulated industries express concern about the speed of GenAI feature rollouts (aiR) outpacing internal review and DPIA processes gartner.com β†—
Reviewers describe support tier ramp as variable; complex Kepler/SDK questions can require escalation through partner success or developer community platform.relativity.com β†—
Customers migrating from on-prem Relativity Server to RelativityOne report data-migration friction, scripting overhead and ARM-based cutover windows relativity.com β†—
Per-workspace artifact IDs change on ARM/clone, breaking partner integrations that hardcode IDs platform.relativity.com β†—