API reference

The core platform API

220 operations across 10 services, read from the running platform on 22 October 2026.

What is in it

Each service, and how many operations it publishes here.


  • Identity

    Sign-in, sessions, MFA, SSO, users, profiles, invites and SCIM.

    82

  • Tenants

    Tenants, memberships, policy, branding, applications, API keys and webhooks.

    36

  • Authorization

    Roles and permissions, ABAC policy rules and access checks.

    11

  • Tokens

    Validate, introspect and revoke access tokens.

    3

  • Events

    The audit and event log, and rules that react to events.

    12

  • Notifications

    In-app, push and email notifications, preferences and device tokens.

    21

  • Chat

    Channels and messages, scoped to a tenant.

    16

  • Wallet

    Wallets, ledger entries and holds with split capture.

    15

  • Queue

    Background tasks with retries and a dead-letter queue.

    7

  • Workflows

    Workflow templates, webhooks and the plugin marketplace.

    17

How to read it

Generated, then curated

We read each service’s OpenAPI document and keep what the gateway exposes to callers. Internal, deprecated and operator-only operations are left out. Requests go to https://api.mergemind.co.

Available is not the same as used

Listing an operation says the code exposes it. The shared core page shows, area by area, whether a product of ours runs on it today.

Core services only

Stores, marketplace, learning and finance have their own APIs, shared during onboarding while their descriptions are brought up to the same standard.

Read-only here

There is no request tester on this page. Developer access comes with a sandbox tenant to try calls against; see the quickstart.