Integrations · APIs & SDKs

Build on top
of the platform

Documented REST API, GraphQL endpoint, JavaScript SDK, and server-side event endpoints. For the long tail of custom integrations, programmatic workflows, and bespoke applications that need direct access to Orbee's data and activation infrastructure.

Read the docs Request developer access
What you can do with the APIs

Programmatic access to every part of the platform

Audiences, native objects, events, identities, reporting — all available through documented endpoints.

Audience operations

Create, query, push, report — all via API.

Trigger an audience build from your CRM event, sync to Google or Meta, then read match rates back — all via API.

  • POST /audiences
  • POST /audiences/{id}/sync
  • GET /audiences/{id}/metrics
Native object CRUD

Read and write your customer model.

Customer table, vehicle table, service order table, plus any custom native objects you've defined.

  • GET /objects/{type}/records
  • Create custom properties
  • Bulk update support
Event ingestion

Server-side endpoints for any source.

Your backend, a third-party tool, an OEM-mandated system — all flow into the same pipeline as Native browser events.

  • POST /events
  • POST /events/batch
  • CAPI + EC forwarding built in
REST · GraphQL · SDK

Three surfaces.
Same data model underneath.

Pick the interface that matches your stack. Every surface speaks the same native object model and identity graph.

REST

Standard REST conventions

JSON in, JSON out. OAuth 2.0 with scoped API keys. Read endpoints under 100ms backed by Quantum.

GraphQL

Type-safe schema

One endpoint at /graphql. Subscriptions for real-time event streams. Schema introspection in non-prod.

JS SDK

First-party tag manager

Powers Native event collection, with hooks for custom event tracking, identity resolution, and consent management.

Server-side endpoints

Push events directly without a browser

For backend integrations, webhook receivers, and OEM-mandated systems — Orbee provides HTTPS endpoints that accept JSON event payloads, with batch endpoints for historical loads.

Real-time events

Single-event endpoint with per-event identity resolution and consent enforcement.

/events

Bulk historical loads

Batch endpoint for backfills and one-time migrations from legacy systems.

/events/batch

CAPI forwarding

Built-in forwarding to Meta CAPI and Google Enhanced Conversions for every server-side event.

CAPI

Identity resolution

Hash and forward emails/phones server-side automatically. Consent state attached per record.

Privacy-aware
Build on top of the platform

Ready for the docs and a developer key?

We'll set up a sandbox account so you can start building.

Request developer access

REST · GraphQL · JS SDK · Server-side