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

Relativity BillingConfiguration API

The BillingConfiguration API from Relativity — 10 operation(s) for billingconfiguration.

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

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

This API exposes 10 operations across 10 paths, and defines 13 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/.

10 operations 10 paths 13 schemas 10 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 BillingConfiguration 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 10

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

BillingConfiguration 10
POST
/api/v1/billing-configuration/product-configurations
Get product configuration
postApiV1BillingConfigurationProductConfigurations body → 200
POST
/api/v1/billing-configuration/package-consumption
Get information about package consumption
postApiV1BillingConfigurationPackageConsumption body → 200
POST
/api/v1/billing-configuration/available-products
Get information about products available for instance
postApiV1BillingConfigurationAvailableProducts body → 200
POST
/api/v1/billing-configuration/available-packages
Get information about packages available for instance
postApiV1BillingConfigurationAvailablePackages body → 200
POST
/api/v1/billing-configuration/products-and-packages-availability
Get information about products and packages availability for instance
postApiV1BillingConfigurationProductsAndPackagesAvailability body → 200
POST
/api/v2/billing-configuration/product-configurations
Get product configuration
postApiV2BillingConfigurationProductConfigurations body → 200
POST
/api/v2/billing-configuration/package-consumption
Get information about package consumption
postApiV2BillingConfigurationPackageConsumption body → 200
POST
/api/v2/billing-configuration/available-products
Get information about products available for instance
postApiV2BillingConfigurationAvailableProducts body → 200
POST
/api/v2/billing-configuration/available-packages
Get information about packages available for instance
postApiV2BillingConfigurationAvailablePackages body → 200
POST
/api/v2/billing-configuration/products-and-packages-availability
Get information about products and packages availability for instance
postApiV2BillingConfigurationProductsAndPackagesAvailability body → 200

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are PackageDetails (7 properties), PackageConsumptionItem (4 properties), GetProductConfigurationRequest (3 properties), GetPackageConsumptionResponse (3 properties). Each schema is shown below with its type and property counts.

ProductConfigurationDetails
object
3 properties
ProductsAndPackagesAvailability
object
2 properties
GetProductsAndPackagesAvailabilityResponse
object
1 property
GetAvailablePackagesResponse
object
1 property
GetProductConfigurationResponse
object
1 property
GetAvailableProductsResponse
object
1 property
PackageConsumptionItem
object
4 properties
GetPackageConsumptionResponse
object
3 properties
PackageDetails
object
7 properties
GetPackageConsumptionRequest
object
2 properties
GetProductsAndPackagesAvailabilityRequest
object
2 properties
GetProductConfigurationRequest
object
Request body used in product-configuration API
3 properties
ProductDetails
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

relativity-billingconfiguration-api-openapi.yml Raw ↑

Other APIs Relativity publishes across the network.

Relativity AnnotationService API
Relativity ArchiveJobs API
Relativity ARM Module v1 API
Relativity ARM Module v3 API
Relativity BillableSummaryReports API
Relativity BillingInsights API
Relativity Client Side Libraries Module API
Relativity ColdStorage API
Relativity CollectAPI API
Relativity Conceptual Analytics v1 API
Relativity Directory API
Relativity Document Configuration Module API
Where this information came from

This is an independent, third-party profile of Relativity BillingConfiguration 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.