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

# Overview

> Introduction to the Events API for ingesting analytics and tracking events.

The Events API provides a flexible interface for ingesting analytics and tracking events. To use this API, you first need to set up an Artie pipeline with `API` as its source type.

## Features

* **Single event tracking**: Send individual events with the `/track` endpoint
* **Bulk event tracking**: Send multiple events in a single request with the `/bulk-track` endpoint
* **Gzip compression**: Bulk requests can be compressed for efficient transmission
* **Deduplication support**: Each event can include a unique `messageId` for deduplication and traceability. If you don't provide one, the server will generate one automatically
* **Single tenant**: Each pipeline gets its own API service deployment, so traffic spikes in one pipeline will not affect latency for other pipelines

## Authentication

All requests require a valid API key in the `Authorization` header. These keys will be generated for you when you set up your pipeline, and should be kept secret.

```
Authorization: Bearer YOUR_API_KEY
```

## Base URL

The base URL for your API instance will be generated and provided to you when you set up your pipeline.

## Next Steps

<CardGroup cols={2}>
  <Card title="Track a single event" icon="arrow-right" href="/api-reference/track-a-single-event">
    Learn how to send individual events
  </Card>

  <Card title="Track multiple events" icon="arrow-right" href="/api-reference/track-multiple-events-in-bulk">
    Learn how to send events in bulk
  </Card>
</CardGroup>