Developers

Built for builders of real-time products.

The APIs, event pipelines, and automation rules that power WeRoll. Integration and developer access is available to approved partners, scoped to the requirements and governance model of each solution.

Request partner access

Event-driven by default

Activity moves through the platform as structured events, so different parts of a solution can react independently to the same change without depending on one another directly.

  1. 01 Services emit events rather than calling each other directly
  2. 02 Context is attached to activity as it enters the platform
  3. 03 Rules evaluate events against state, timing, and permissions
  4. 04 Governance applies at every stage, not as a final check

API surface

Event ingestion

Publish activity into the platform

Services can emit events using queue-based publishing, signed HTTP ingestion endpoints, and public hook tokens for integrations.

Event delivery

Subscribe and react to activity

  • Subscriptions and routing
  • Delivery processing
  • Retry semantics
  • Replay and testing tools
  • Idempotent handling

Presence APIs

Live state, availability, and activity

Read and write operational state — availability, operating status, schedules, sessions, and location-associated activity.

Automation APIs

Rules, triggers, and workflows

  • Rule definition
  • Trigger conditions
  • Notification dispatch
  • Workflow initiation
  • Proximity subscriptions

Documentation and console access are provided to approved partners during onboarding.