> ## Documentation Index
> Fetch the complete documentation index at: https://docs.ellipsis1.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Ingestion API

> Learn how the Ellipsis SDK connects to the E1 telemetry ingestion API.

## Description

The E1 Ingestion API provides the entry point for telemetry data collected by the Ellipsis SDK.

It enables instrumented applications to securely transmit agent execution data to the E1 observability platform, where traces and associated telemetry are processed and made available in your organization's workspace.

## API endpoint

The Ellipsis SDK uses the following endpoint to export telemetry:

| Property | Value |
| - | - |
| API endpoint | `YOUR_E1_INGESTION_API_URL` |
| Protocol | HTTPS |
| Authentication | Agent API key |
| Used by | Ellipsis SDK |

The endpoint is configured during SDK initialization through the `ingestionUrl` parameter.

## Authentication

Requests sent to the E1 Ingestion API must be authenticated using an agent API key.

Each agent API key is generated from your E1 organization workspace and associates incoming telemetry with the corresponding agent.

To obtain your API key:

1. Sign in to your [E1 account](https://app.ellipsis1.com).
2. Open your organization's workspace.
3. Create or select an agent.
4. Generate an agent API key.

The API key must be provided when initializing the Ellipsis SDK.

> [!WARNING]
>
> **Security recommendation:** Never expose your agent API key in client-side
> applications, public repositories or source-controlled configuration files.
> Store credentials in environment variables or a secure secrets manager.

## SDK configuration

The ingestion endpoint and agent API key are mandatory configuration parameters.

```typescript theme={null}
import { initEllipsis, type Config } from "@ellipsis1/sdk";

const config: Config = {
  ingestionUrl: process.env.ELLIPSIS_INGESTION_URL!,
  apiKey: process.env.ELLIPSIS_AGENT_API_KEY!,
};

const ellipsis = initEllipsis(config);
```

Once initialized, the SDK uses these configuration values to establish the connection with the E1 platform and export collected telemetry.

## Telemetry export

The Ellipsis SDK acts as the instrumentation and telemetry export layer between your application and E1.

During supported agent executions, the SDK collects and organizes telemetry into structured traces and spans.

Collected information can include:

* Agent and chain execution events.
* LLM invocations and model information.
* Tool calls and associated operations.
* Token consumption and execution duration.
* Latency and cost information.
* Errors and failed executions.

The SDK batches telemetry before transmission and includes retry mechanisms to handle transient network failures.

## Data availability

Once telemetry has been successfully exported and processed, it becomes available in the corresponding E1 workspace.

The collected data is organized by project and by agent, and made available for inspection through the E1 observability interface.

Data retention is determined by your E1 subscription plan.

## Related documentation

* [Quickstart](https://docs.ellipsis1.com/quickstart.md)
* [TypeScript SDK](https://docs.ellipsis1.com/sdk/typescript.md)
* [First example: Weather Agent](https://docs.ellipsis1.com/examples/weather-agent.md)
* [E1 Workspace](https://app.ellipsis1.com)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.