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

# Events API Overview

> Send customer events and profile data to RevBridge AI through a simple REST API.

## What is the Events API?

The Events API is RevBridge AI's data ingestion endpoint. It lets you send customer events — purchases, page views, sign-ups, and any custom action — along with user profile data directly from your application.

Once ingested, this data powers:

* **Unified Customer Profiles** — every event is linked to a customer identity, building a 360-degree view.
* **Dynamic Segments** — audiences are automatically updated based on real-time behavioral data.
* **AI Campaigns** — the optimization engine uses your event data to personalize messaging, timing, and channel selection.

```mermaid theme={null}
flowchart LR
    A(["Your App<br/>Backend"]) -->|POST /ingest/events| B(["Events API"])
    B --> C{{"RevBridge AI"}}
    C --> D["Profiles"]
    C --> E["Segments"]
    C --> F["Campaigns"]

    classDef source fill:#EEF2FF,stroke:#4F46E5,stroke-width:2px,color:#1E1B4B;
    classDef api fill:#ECFDF5,stroke:#059669,stroke-width:2px,color:#064E3B;
    classDef core fill:#FEF3C7,stroke:#D97706,stroke-width:2px,color:#78350F;
    classDef output fill:#F1F5F9,stroke:#475569,stroke-width:1.5px,color:#0F172A;

    class A source;
    class B api;
    class C core;
    class D,E,F output;
```

<Info>
  The Events API is for server-side ingestion. To capture events directly from a website or web app in the browser, use the [Web SDK](/developer/web-sdk) — it sends to the same pipeline with a browser-safe publishable key.
</Info>

## Use cases

<CardGroup cols={2}>
  <Card title="E-commerce" icon="cart-shopping">
    Track purchases, cart events, product views, and wishlist actions to drive personalized product recommendations and win-back campaigns.
  </Card>

  <Card title="Mobile Apps" icon="mobile">
    Send in-app events like screen views, feature usage, and subscription changes to trigger behavior-based push notifications.
  </Card>

  <Card title="SaaS Platforms" icon="laptop-code">
    Ingest sign-ups, feature adoption, and billing events to power onboarding sequences and churn prevention campaigns.
  </Card>

  <Card title="Omnichannel Retail" icon="store">
    Unify online and offline events — POS transactions, loyalty actions, and website activity — into a single customer profile.
  </Card>
</CardGroup>

## How it works

<Steps>
  <Step title="Authenticate">
    Include your API key in every request. [Set up authentication →](/developer/authentication)
  </Step>

  <Step title="Send events">
    POST user events to the `/ingest/events` endpoint with user identifiers and event data. [Learn the payload format →](/developer/ingesting-events)
  </Step>

  <Step title="Identify users">
    Attach at least one identifier (email, user ID, phone) so events are linked to the right customer profile. [See identification rules →](/developer/user-identification)
  </Step>

  <Step title="RevBridge processes your data">
    Events are validated, linked to customer profiles, and made available across Segments, Campaigns, and Analytics — typically within seconds.
  </Step>
</Steps>

## Next steps

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/developer/authentication">
    Generate API keys and authenticate your requests.
  </Card>

  <Card title="Ingesting Events" icon="paper-plane" href="/developer/ingesting-events">
    Full payload reference with code examples.
  </Card>

  <Card title="User Identification" icon="fingerprint" href="/developer/user-identification">
    How customer identity resolution works.
  </Card>

  <Card title="Event Types" icon="list" href="/developer/event-types">
    Common event schemas and custom properties.
  </Card>
</CardGroup>