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

# Events Introduction

> HTTP API for server-side event tracking and user profiles

Welcome to the Zixflow Events API. Use this service to send server-side events and manage user profiles.

> **Who this is for:** Backend developers and integrators sending server-side events. Mobile and web app actions should use an [SDK](/documentation/sdk/javascript/introduction) instead.

## Base URL

All Events API endpoints are available at:

```
https://api-events.zixflow.com
```

<Note>
  Events APIs use a different host and authentication scheme than messaging ingest (`api-ai.zixflow.com` with `x-api-key` / `x-workspace-id`). See [Events Authentication](/api-reference/zixflow-ai/events/authentication).
</Note>

## API vs SDK

|                 | SDKs                          | HTTP API                                                         |
| --------------- | ----------------------------- | ---------------------------------------------------------------- |
| **Who uses it** | Web and mobile apps           | Backend servers, scripts, integrations                           |
| **Auth**        | API key in SDK initialization | `Authorization: Basic base64(api_key:)`                          |
| **Batching**    | Automatic                     | Manual via [`/v1/batch`](/api-reference/zixflow-ai/events/batch) |
| **When to use** | User-facing app actions       | Server-side events and profile updates from backend              |

**Rule of thumb:** If the event happens because a user tapped something in your app, use an SDK. If it happens on your server (fulfillment, billing, fraud detection), use this API.

## API Groups

| Group              | Base path | Purpose                                                     |
| ------------------ | --------- | ----------------------------------------------------------- |
| **Data Pipelines** | `/v1/`    | Segment-compatible identify, track, screen, page, and batch |

Group and Alias are **not supported**.

## Data Pipelines (`/v1/`)

* [Identify](/api-reference/zixflow-ai/events/identify) — Create or update a user profile
* [Track](/api-reference/zixflow-ai/events/track) — Record a user action or business event
* [Screen](/api-reference/zixflow-ai/events/screen) — Record a mobile screen view
* [Page](/api-reference/zixflow-ai/events/page) — Record a web page view
* [Batch](/api-reference/zixflow-ai/events/batch) — Send multiple events in one request

All Data Pipelines requests accept `Content-Type: application/json`. Successful responses return `HTTP 200` with an empty body `{}`.

## Getting Started

1. Obtain your API key from the Zixflow dashboard (Workspace Settings → API Keys).
2. Authenticate with Basic Auth. See [Events Authentication](/api-reference/zixflow-ai/events/authentication).
3. Send events with the Data Pipelines endpoints above.
4. Handle errors using the shared [Events Errors](/api-reference/zixflow-ai/events/errors) reference.

For device, OS, app, IP, locale, and campaign fields, see [Context Object](/api-reference/zixflow-ai/events/context).

## Conceptual Guides

For product concepts (identity, attributes, devices, scenarios), see the [Events documentation](/documentation/events/getting-started) and the [Event API conceptual reference](/documentation/events/event-api-reference).