Help Center

Do you provide SDK or API access for custom workflows?

Yes — the same APIs the BetterSuite team uses to build the platform are exposed to your team. Anything the apps and admin console can do, your own services can do via the federated GraphQL API and webhooks.

Reading time
4 min
Last updated
April 15, 2026
Sections
3 on this page
01

The federated GraphQL API

BetterSuite exposes a single GraphQL endpoint that federates 21 production services. The schema is published and type-checked end to end — your client library is generated from the same source the platform team uses.

Authentication uses scoped API keys for server-to-server access and OAuth-style flows for user-facing integrations. Rate limits are tenant-aware and configurable.

02

Client SDK for product surfaces

If you're building custom product surfaces — a branded analytics portal, a marketing tool, an internal operator dashboard — the Flutter and Dart SDK gives you typed repositories and a working authentication flow without re-implementing the API surface.

03

Webhooks for downstream workflows

For workflows that react to platform events, subscribe to webhooks rather than polling the API. Events are delivered with retries and signed payloads, and you can scope subscriptions per resource type to avoid noisy fan-out.

Was this article helpful?

Need something more specific?

If your scenario goes beyond what the articles cover, walk us through it and the team will come back with a draft plan.

Contact the team

Build the foundation once. Expand without limits.

BetterSuite is built for teams who see on-demand as a business — not a feature.