> For the complete documentation index, see [llms.txt](https://docs.revenium.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.revenium.io/integrations/api-data-sources.md).

# 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](/get-started/quickstart/api-data-sources-and-otlp.md). For full endpoint details, use [OTLP Integration](/integrations/otlp-integration.md).

## 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](/integrations/api-key-permissions.md)     |
| Add metering to app code         | [SDK Setup](/integrations/sdk-setup.md)                         |
| Send OpenTelemetry spans or logs | [OTLP Integration](/integrations/otlp-integration.md)           |
| Connect provider billing data    | [Provider Integrations](/integrations/provider-integrations.md) |
| Validate direct API payloads     | [API Reference](https://revenium.readme.io)                     |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.revenium.io/integrations/api-data-sources.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.