Docs

Quickstart

Everything below runs against the live API. Keys are issued with waitlist invites while I'm in beta — join here and you'll get one with your invite email.

1. One key, plain HTTPS

Every service is a resource under api.plurism.dev, authenticated with a Bearer key scoped per project. Create a support thread:

curl -X POST https://api.plurism.dev/support/threads \
  -H "Authorization: Bearer $PLURISM_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "body": "Reset password button does nothing on Safari",
    "category": "bug",
    "reporter_email": "user@example.com",
    "reporter_name": "Alice"
  }'

The response includes a public ref (like ACME-42) your user can use on the hosted lookup page — replies flow back over email automatically.

2. Or the typed SDK

The TypeScript SDK covers support, waitlist, feedback, flags, content, changelog and files. Server-side only — never ship your key to a browser.

import { createPlurismClient } from "@plurism/sdk";

const plurism = createPlurismClient({
  baseUrl: "https://api.plurism.dev",
  apiKey: process.env.PLURISM_API_KEY!, // server-side only
});

// Support thread (returns a public ref like ACME-42)
const thread = await plurism.support.threads.create({
  body: "Reset password button does nothing on Safari",
  category: "bug",
  reporter_email: "user@example.com",
  reporter_name: "Alice",
});

// Waitlist signup
await plurism.waitlist.add({ email: "early@adopter.dev", referrer: "x" });

// Feedback
await plurism.feedback.submit({ rating: 9, comment: "Love it" });

// Feature flag
const flag = await plurism.flags.evaluate("new-checkout", { user_id: "u_1" });

3. On Cloudflare Workers? Skip the network

If your backend is a Worker, a service binding gives you zero-egress, single-digit-ms calls:

// wrangler.jsonc — zero-egress if your backend is a CF Worker
{ "services": [{ "binding": "PLURISM", "service": "plurism-api" }] }

// then:
const plurism = createPlurismClient({
  binding: env.PLURISM,
  apiKey: env.PLURISM_API_KEY,
});

What's covered today

• Support inbox — threads, replies, statuses, tags, inbound email, public lookup page. Full REST surface.
• Analytics — first-party traffic, acquisition, funnel, and revenue analytics via a lightweight pixel + dashboard.
• Waitlist — signup, list, invite (fires the invite email).
• Feedback — ratings + comments with stats.
• Feature flags — CRUD + edge-cached evaluate.
• Content — blog, news, FAQ, and how-to with server-rendered HTML + schema.org JSON-LD for SEO/AEO.
• Changelog — public JSON feed you can embed.
• Files — upload and stream in and out, allow-listed types with SVG scrub.
• Webhooks, email notifiers — API-first today; portal UI is rolling out.

Full API reference is being published service-by-service. Anything unclear in the meantime — ask me, replies usually land same-day.