Superchat
MESSAGING · MESSAGING
Send a message, update a contact, and read webhook subscriptions in the account they connected.
Connect Superchat with Fabriq Developer
Your user pastes their Superchat credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Superchat in practice
Superchat has exactly one credential and no scopes — the documentation says the token "is currently scoped to have global read and write access" — and the entire workspace shares 2,500 requests per 5-minute interval across every key, so minting more keys adds no throughput. Reaching the token at all needs administrator login.
Scopes that draw scrutiny
X-API-KEYThe only credential. Superchat’s own wording: "The token is currently scoped to have global read and write access." A read-only agent still holds write access to every conversation.
Rate limits
- "Each workspace is allocated 2500 requests per 5-minute interval."
- The allowance is collective across all API keys in the workspace, not per key.
- Over the threshold all requests are rejected with 429 until the next 5-minute window opens.
Who has to approve
The token lives under Settings > API in the web app and administrator login credentials are needed to reach that page, so an ordinary user cannot self-serve a key — someone with admin rights has to issue it.
Worth knowing
- HTTPS is mandatory; plain HTTP requests are rejected rather than upgraded.
- Because the quota is per workspace, an unrelated internal script can exhaust an agent’s budget and there is no per-key accounting to prove it.
- Webhook subscriptions are fully API-managed (list, create, update, get, delete), so an integration can silently add its own delivery target.
- No scope system means least privilege is not available at all — the only lever is who holds the key.
Checked against Authentication (2026-09-29), Rate limiting (2026-09-29), Superchat API documentation index (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Superchat behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.