How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Relativity

Relativity BillingInsights API

The BillingInsights API from Relativity — 6 operation(s) for billinginsights.

Documentation Provider Profile APIs.io OpenAPI GitHub

Relativity BillingInsights API is one of 52 APIs that Relativity publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include BillingInsights. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, rate-limit docs, and a getting-started guide.

This API exposes 6 operations across 6 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against 2 base URLs: https://billing-insights.api.relativity.one/billing-drilldown-api, https://services.vaus.relativityone.us/billing-drilldown-api/.

6 operations 6 paths 26 schemas 2 GET4 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{host}/Relativity.REST/api/relativity-object-model/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Relativity BillingInsights API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated, though some operations may also be called without credentials.

  • bearerAuth — JWT Authorization header using the Bearer scheme.

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 2 GET, 4 POST. Each is listed below with its method, path, parameters, and response codes.

BillingInsights 6
GET
/api/v1/billing-insights/hierarchy-lookup/{level}
Get artifact ids
getApiV1BillingInsightsHierarchyLookupByLevel 3 params → 200
POST
/api/v1/billing-insights/month-details
Get monthly billing metrics
postApiV1BillingInsightsMonthDetails body → 200
POST
/api/v1/billing-insights/users-details
Get a user list
postApiV1BillingInsightsUsersDetails body → 200
GET
/api/v2/billing-insights/hierarchy-lookup/{level}
Get artifact ids
getApiV2BillingInsightsHierarchyLookupByLevel 3 params → 200
POST
/api/v2/billing-insights/month-details
Get monthly billing metrics
postApiV2BillingInsightsMonthDetails body → 200
POST
/api/v2/billing-insights/users-details
Get a user list
postApiV2BillingInsightsUsersDetails body → 200

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are GetUsersDetailsResponseItem (12 properties), Workspace_2 (11 properties), GetMonthDetailsRequest (10 properties), Workspace (10 properties). Each schema is shown below with its type and property counts.

GetUsersDetailsResponseItem
object
12 properties
SinglePricedMetric
object
7 properties
GetUsersDetailsResponse
object
2 properties
Workspace
object
Workspace information
10 properties
Matter
object
Matter information
5 properties
GetHierarchyLookupResponse
object
1 property
SingleUsageMetric
object
5 properties
HierarchyItemSelector
object
Specifies item to select. instanceID must be provided, additionally depending on the chosen level must be provided clientArtifactID, matterArtifactID or worksp…
5 properties
Instance
object
Instance information
3 properties
Client
object
Client information.
6 properties
MetricMetadata
object
3 properties
GetMonthDetailsRequest
object
Request body used in month-details API
10 properties
GetMonthDetailsResponseItem
object
9 properties
UserInstanceSpecificData
object
4 properties
Contract
object
Contract information
2 properties
PagingRequest
object
Specifies paging options - top and skip values need to be either empty or populated. Specifying just a single value is considered a bad request. - if top and s…
5 properties
GetMonthDetailsResponse
object
3 properties
GetHierarchyLookupResponseItem
object
4 properties
ClientMatterData
object
2 properties
PagingResponse
object
Paging information about the response. If the caller wants to obtain the rest of the result set there should be subsequent request made with same parameters an…
2 properties
FieldFilter
object
Field filter information
3 properties
SingleSubMetric
object
2 properties
GetUsersDetailsRequest
object
Request body used in users-details API
8 properties
FieldOrder
object
Allows to specify order that should be applied to the query result
2 properties
Money
object
2 properties
Workspace_2
object
Workspace information
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relativity-billinginsights-api-openapi.yml Raw ↑

Other APIs Relativity publishes across the network.

Relativity AnnotationService API
AE Profile APIs.io
Relativity ArchiveJobs API
AE Profile APIs.io
Relativity ARM Module v1 API
AE Profile APIs.io
Relativity ARM Module v3 API
AE Profile APIs.io
Relativity BillableSummaryReports API
AE Profile APIs.io
Relativity BillingConfiguration API
AE Profile APIs.io
Relativity Client Side Libraries Module API
AE Profile APIs.io
Relativity ColdStorage API
AE Profile APIs.io
Relativity CollectAPI API
AE Profile APIs.io
Relativity Conceptual Analytics v1 API
AE Profile APIs.io
Relativity Directory API
AE Profile APIs.io
Relativity Document Configuration Module API
AE Profile APIs.io
#BillingInsights
← Back to R APIs
API Details
ID
relativity:relativity-billinginsights-api
Base URL
https://{host}/Relativity.REST/api/relativity-object-model/v1
Docs
https://platform.relativity.com/RelativityOne/Content/REST_API/REST_API.htm
Provider
Relativity
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=relativity-billinginsights-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/relativity-billinginsights-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Relativity BillingInsights API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.