API Data Sources

Use this page to understand the data-source records Revenium creates for instrumented applications, provider accounts, and external API sources. For the first OTLP setup, start with API Data Sources & OTLP. For full endpoint details, use OTLP Integration.

What a Data Source Represents

A data source identifies where usage data enters Revenium. It can represent:

• An application or service emitting telemetry through an SDK or OTLP exporter.

• A provider account connected for billing and historical usage import.

• A direct API integration that sends metering payloads to Revenium.

The data source gives Revenium a stable place to attach environment, owner, version, and metering identifiers. Those identifiers are then used by logs, traces, charts, alerts, and cost attribution.

Fields You Will Use

Field	Use it for
Source type	Distinguishes AI, provider, API, or other source categories.
Source name	Human-readable name shown in the product.
Environment	Separates production, staging, development, and other contexts.
Metering ID	Identifier used when configuring SDKs, agents, middleware, or external sources.
Version	Optional version marker for source-level tracking.

Where To Go Next

Need	Page
Create or manage API keys	API Key Permissions
Add metering to app code	SDK Setup
Send OpenTelemetry spans, logs, or metrics	OTLP Integration
Connect provider billing data	Provider Integrations
Validate direct API payloads	API Reference