ReactifySDK · Reference

Production architecture

ReactifySDK is a browser-delivered experience backed by first-party APIs. This page describes the runtime data plane, storage, and trust boundaries— separate from the ReactionSDK overlay pipeline.

Edge delivery

Host sites load reactify.js from the CDN. The bundle registers reactify-thread and resolves templates or threads through public JSON endpoints. No secrets ship to anonymous viewers.

Viewer browser

flowchart LR
  Host[Publisher site] --> Script[reactify.js CDN]
  Script --> CE[Custom elements]
  CE --> API[GET /api/reactify/threads/...]
  CE --> EVT[POST /api/reactify/events]

Paste into mermaid.live to render.

Uploads & media

Creator-authenticated routes mint short-lived presigned URLs. Clients PUT bytes directly to object storage; API rows reference reactify_videos for playback signing and poster generation.

Presigned upload

sequenceDiagram
  participant C as Creator client
  participant A as /api/reactify/upload-url
  participant S as Object storage
  C->>A: POST purpose + content type
  A->>C: presigned PUT URL
  C->>S: PUT media bytes
  C->>A: PATCH thread with video id

Paste into mermaid.live to render.

Data stores

MongoDB — threads, reactions, templates, widgets, Reactify events, stats counters, and marketplace indices ( collections under lib/db.ts).
Object storage — originals, reaction clips, posters; served via signed GETs.

Creator dashboard auth

Dashboard APIs read Authorization: Bearer … JWTs minted for Reactify creators (lib/reactify-dashboard-token.ts). Public embed traffic never receives these tokens.

Operational checklist

Version the CDN bundle; communicate breaking changes with semver and release notes.
Monitor POST /api/reactify/events error rates and payload validation failures.
Keep CORS and CSP documentation next to your embed generator for enterprise customers.

API index: API reference