Send any event or attribute into Compass, safely and predictably.
For developers and platform operators: a versioned ingest API and typed SDK for streaming customer events from any system, with the validation, scoping, and idempotency you expect from production infrastructure.
Built for production ingestion
Everything you need to make Compass a reliable destination for your customer events — versioned, validated, and safe to retry.
Ingest endpoint
A single, documented endpoint for streaming customer events and attributes into Compass.
Versioned event envelopes
Every event is wrapped in a versioned envelope, so schema changes never break existing producers.
Schema registration
Register the event types you send up front and validate payloads against them on the way in.
Scoped API keys
Issue keys limited to specific providers and actions, with rotation and revocation.
Idempotency
Supply an idempotency key and safely retry — duplicate deliveries collapse into one event.
Provider namespacing
Each source writes into its own namespace, so events never collide across integrations.
Client SDK
A typed SDK that handles auth, batching, retries, and envelope construction for you.
Identity identifiers
Send emails, phone numbers, or your own IDs and let Compass resolve them to one profile.
Event validation
Payloads are validated against registered schemas before they touch a profile.
Error handling
Clear, structured error responses tell you exactly what to fix, with predictable status codes.
From schema to resolved profile
- 1
Register your schemas
Declare the event types your system emits so Compass can validate every payload you send.
- 2
Mint a scoped key
Create an API key limited to your provider namespace and the actions it needs — nothing more.
- 3
Send events with idempotency
POST versioned envelopes to the ingest endpoint, each with an idempotency key so retries are safe.
- 4
Resolve and enrich
Compass validates the event, resolves the identity, and updates the unified profile within seconds.
One profile, no duplicates
Send whichever identifiers you have — email, phone, or your own customer ID — and Compass resolves them to a single profile. Idempotency keys make delivery exactly-once from your side, even across retries and network failures.
- Multiple identity identifiers per event
- Deterministic resolution to a unified profile
- Idempotency keys collapse duplicate deliveries
- Provider namespacing keeps sources isolated
Start streaming events into Compass.
Register a schema, mint a scoped key, and send your first validated event today.