Skip to main content
Fourth Dimension Operating System (4D OS) is a platform that provides organizations with a comprehensive set of tools to manage fan engagement, loyalty, rewards, consent, and more. Your organization brings its members; 4D gives you one place to hold their identity, track how they engage, reward that engagement with XP, and respect their consent choices throughout - with an on-chain XP token settling behind the scenes. You integrate through our REST API, authenticated with an organization API key, and there is a lightweight engagement SDK for browser event tracking. Everything your key touches is scoped to your organization: your members, your events, your XP economy.

​
The pieces

  • Members - each person in your member base holds a single 4D identity, attached to your organization as a member. See Members.
  • Events - engagement events flow in from your sites and apps (a publishable tracking key, batched browser events) and drive everything downstream. See Events.
  • XP - a double-entry loyalty ledger. Rules turn events into XP awards; tiers rank members; balances settle to an on-chain token. See XP.
  • Consent - append-only consent records gate what the platform does with member data. See Consent.
  • Tenants - your organization is an isolated tenant, with multi-tenancy support for multi-team organisations. See Tenants.
  • Content - articles written in the 4D console, read over HTTP and rendered on your own website. See Content API.

​
Start here

Quickstart

Make your first authenticated call in five minutes.

Create a user

Add a member to your organization, idempotently.

Trigger an event

Track engagement from a browser with a publishable key.

Migrate an existing member base

Bulk-import your current members - never overwrites, never emails, never deletes.

​
API reference

The API reference is generated live from the same schemas the server validates against, so it cannot drift from what the API actually accepts.

​
Private modules

If the standard API, SDK, and bulk import don’t fit your setup, a partner admin can publish a private module owned by your organization and install it for your own tenant. The module can declare native event types and send signed events through the module ingest surface. Start with Publish a private module, then use the API reference for the complete route schemas and responses.