Build on SocialHub
Connect your AI agents over a governed MCP server, operate the platform from Claude Code with SoCode, and integrate through the REST API and member-portal embed. Tenant-key authenticated, scoped per tool, every call audited.
# add the governed MCP server
$ claude mcp add --transport http flash \
https://flash.socialhub.ai/api/mcp \
--header "Authorization: Bearer $FLASH_API_KEY"▋
tenant key required · scoped per tool · audited
Developer resources
Get started
Authenticate once and make your first call — the tenant-key-authenticated v2 REST API, its full reference, and key management.
Quick Start
From zero to your first authenticated call — create a key, pick your scopes, and make a request.
Start here →REST API Reference
Programmatic access to members, stores, orders, loyalty, coupons and campaigns over a tenant-key-authenticated REST API.
Browse the API →API Keys
Create and scope tenant API keys (fl_live_…), pick read-only or write presets, and review recent activity.
Manage keys →Extend the platform
Build on Flash without forking it — your workspace's own data objects, real-time webhooks, no-code connectors, and per-workspace custom fields & modules.
Custom Objects API
Read and write a workspace's own custom objects: discover object types and their self-describing field schema (GET /api/v2/objects, objects:read), then list, create, update and delete records (objects:write) — schema-validated, with a fail-closed write guard.
Read the objects guide →Webhooks
Subscribe your systems to Flash events: register endpoints (POST /api/v2/webhooks, webhooks:manage), discover events (GET /api/v2/events/catalog), verify Standard Webhooks HMAC-SHA256 signatures, dedupe by webhook-id, and rely on retries + a delivery log. Thin, non-PII payloads.
Read the webhooks guide →Zapier & Make Connectors
Connect Flash to thousands of apps with no code: triggers are Flash webhook events (subscribed over the REST Hook contract), actions are v2 REST endpoints, and auth is a scoped fl_live_ API key.
Read the connector guide →Customization: Fields & Modules
The two ways Flash is shaped per workspace without forking: custom member fields set through the API (customAttributes), and optional modules gated per workspace by server-enforced entitlements.
Read the guide →AI agents & natural language
Operate SocialHub and query your governed metrics conversationally — in your IDE, in Slack, or from any MCP client.
SoCode — Run SocialHub from Claude Code
A downloadable skill plus a governed MCP server. Operate SocialHub and query your metrics in natural language, right from Claude Code, Claude Desktop or Cursor.
Open the guide →SoTag — Run SocialHub from Slack
Your AI retention colleague in Slack. Install, run /so connect to bind a channel to your team, then ask your governed metrics and approve the actions it drafts.
Set up SoTag →MCP Integration
The full Model Context Protocol reference — endpoint, transport, authentication, and the governed tools your AI agents can call.
Read the MCP guide →SoClaw Win-Back Integration
Run an autonomous win-back agent against Flash: the claim → context → lever → note → complete loop, a scoped + capped agent key, self-deploying the OpenClaw runtime with the SoClaw skill, the server-side safety boundary, and the error codes.
Read the win-back guide →Commerce & data integration
Connect the systems you sell and operate through — e-commerce channels, your POS / OMS / ERP, and the real-time data foundation underneath.
Shopify · Amazon · TikTok Shop
Connect your e-commerce channels: sync Shopify products and earn points on orders automatically, and let members earn points for verified Amazon and TikTok Shop orders. Where each credential comes from and how to configure it.
Read the channel guide →POS · OMS · ERP Integration
Wire your point-of-sale, order-management and ERP systems into loyalty over the v2 REST API — award points on a sale, refund claw-backs, and reconcile stores, members and the points ledger.
Read the integration guide →Data Architecture
How CRM transactions, SDK behavior streams, third-party systems, Kafka, Flink and StarRocks become one real-time customer data foundation.
See the architecture →Embed, push & wallet
Put loyalty inside your storefront and native app, reach members on push, and issue wallet cards. Each is an independent building block — adopt one, some, or all.
Member Portal Embed
Embed the loyalty member portal into your own storefront, site, or native app (web view + single sign-on). Includes the optional native packages that wrap it.
See the embed →Web Tracking SDK
Drop a first-party beacon on your own marketing or e-commerce site — page views flow into the member behavior timeline, with server-side device, geo and bot enrichment. No key, GPC-respecting.
Get the snippet →App Push
Register device tokens and let push join the same automation/send stack as email — fail-open channel waterfall, one shared frequency cap.
Read the push guide →Wallet (Apple & Google)
Issue a branded membership card to Apple Wallet (.pkpass, auto-updating) or Google Wallet (save link) server-side, from one endpoint.
See Wallet →Location (LBS)
Member-keyed store visits, store/region targeting, and consent-gated geofence endpoints — privacy-first, fail-closed, no raw coordinates.
Read the LBS guide →Security & compliance
The controls and consent surfaces underneath everything — data-security architecture and the published privacy / consent API.
Data Security Management
Cross-cutting controls for API and SDK ingestion, event transport, stream processing, MPP serving, application access, marketing activation and audit operations.
Review the controls →Compliance & Consent API
Read the published member privacy / compliance statement (current, history, a version) and verify a member's consent — scoped privacy:read / consent:read, drafts never exposed.
Read the guide →Have a technical question?
Talk to an engineer about MCP scopes, governance, or fitting SocialHub into your AI stack.
Talk to engineering