For developers
Everything in the UI is an API
One action registry powers the interface, Molly, and a token-authed REST API — 165 actions across 19 features, described by an OpenAPI 3.1 spec, guarded by scoped tokens that never exceed the caller's live permissions.
REST API
Records, queries, and every feature action
Create and update records on any object, run SOQL from code, and invoke the same feature actions the UI uses — send a broadcast, schedule a post, create a task, move a pipeline stage. Straight REST with JSON, discoverable via the generated OpenAPI 3.1 document.
- Generated OpenAPI 3.1 spec
- Cursor pagination and consistent envelopes
- SOQL / SOSL / SAQL over HTTP
- The exact routes the product itself runs on
# Create a record
curl -X POST https://api.klerc.co/api/v1/records/reservation \
-H "Authorization: Bearer wk_live_..." \
-H "Content-Type: application/json" \
-d '{"data": {"guest": "Ava Chen", "check_in_date": "2026-09-01"}}'
# Query with SOQL
curl -X POST https://api.klerc.co/api/v1/query \
-H "Authorization: Bearer wk_live_..." \
-d '{"q": "SELECT brand, SUM(total_amount) FROM reservation GROUP BY brand"}'Tokens & scopes
Scoped tokens that respect reality
Access tokens are hashed at rest and scoped as feature × action — records:create, publishing:schedule, inbox:reply. At request time a token's scopes intersect with the owner's live permissions, so revoking a person's access revokes their integrations too. Manage everything in Settings → Developer.
- sha256-hashed tokens, wk_live_ prefix
- Scope picker per token
- Live-permission intersection at request time
- Per-user Molly token auto-provisioned
wk_live_3f9a... # token prefix scopes: - records:read - records:create - query:run - publishing:schedule - inbox:reply
Integrations
30+ connectors, two clicks each
The integrations hub connects email, messaging, social, commerce and calendar accounts through managed OAuth — with connected-account status, per-account settings and disconnect in one place. These connections power the inbox, publishing, commerce sync, calendar sync and agent tools.
- Managed OAuth broker + direct OAuth connectors
- Encrypted token storage
- Per-account routing and settings
- Category-filtered catalog UI
Realtime & jobs
Sockets and queues where they belong
Presence, live co-editing, and inbox updates ride WebSockets with a Redis adapter; heavy work — sends, syncs, ingestion, publishing — runs on background queues with retries and sweepers. Voice and video use a mediasoup SFU with TURN credentials minted per session.
- Socket namespaces for app + anonymous public clients
- Queued jobs with retry + poller sweepers
- Doc/sheet collab with total-order sequencing
- SFU-based voice/video rooms
Developer ergonomics
Action registry
One catalog of every action — the UI, Molly and the API all call through it.
Molly dispatcher
listActions / describeAction / performAction — your integration can discover capabilities.
Consistent envelopes
Uniform success/error shapes with status and data keys.
Rate limits
Sensible defaults: auth 20/15min, API 600/min per IP.
Webhook ingest
Idempotent inbound processing for commerce and messaging events.
Public clients
Forms and chat widgets embed anywhere with origin allow-lists.
Works better together
Related modules
Run your whole business from one tab.
Join the early access — bring your team, connect your channels, and keep every workflow in one place.