Integrations & API
Connecting to other tools, API keys, and webhooks.
API keys and webhooks
How to create API keys and configure webhooks for integrations.
API Keys
Go to Settings → API to create scoped API keys. Each key can have specific permissions (read/write for members, events, broadcasts).
Webhooks
Configure webhook URLs to receive real-time notifications when members are created, payments succeed, or events are published. All payloads are signed with HMAC-SHA256.
REST API
See the full API Reference in Settings → API → Docs for endpoints, rate limits, pagination, and example curl commands.
Connecting Integrations
Connect Mybers to the other tools your organization uses from the managed integration library.
The integration library
Mybers offers a managed library of integrations under Settings → Integrations. Each listing shows what the integration does and what it syncs.
Connecting one
Choose an integration and select Connect. Most use a guided OAuth flow — you authorize Mybers in the other tool's window and you're done. Once connected, you configure what data flows and in which direction.
Self-serve vs managed
Many integrations are self-serve: connect them yourself in a few minutes. More involved ones can be set up as a managed install, where the Mybers team configures it for you. Integrations can also be offered white-label or branded for your organization.
You can disconnect any integration at any time; doing so stops future syncing but doesn't delete data already in Mybers.
Using Webhooks
Send real-time event notifications from Mybers to your own systems with webhooks.
What webhooks do
A webhook sends a real-time HTTP request to a URL you control whenever something happens in Mybers — a member joins, a payment succeeds, an event registration comes in. They're the way to push Mybers data into custom systems.
Setting one up
Under Settings → Webhooks, add an endpoint URL and choose which events to subscribe to. Mybers will POST a JSON payload to that URL each time a subscribed event fires.
Verifying and retrying
Each webhook is signed with a secret so your endpoint can verify the request genuinely came from Mybers. If your endpoint is down or returns an error, Mybers retries with backoff and logs every delivery attempt so you can inspect and replay failures.
Always verify the signature before trusting a payload, and return a 2xx response quickly — do heavy processing asynchronously.
Single Sign-On with OIDC
Let your team sign in to Mybers through your identity provider using OIDC.
Single sign-on
Single sign-on (SSO) lets your team log in to Mybers with your existing identity provider instead of a separate password. Mybers supports SSO via OIDC (OpenID Connect), which works with providers like Okta, Microsoft Entra ID, and Google Workspace.
Setting it up
Under Settings → Security → SSO, create an OIDC application in your identity provider, then paste its client ID, client secret, and issuer URL into Mybers. Mybers supplies the redirect URI to register on the provider side.
How sign-in works
Once enabled, team members sign in by being redirected to your provider, authenticating there, and returning to Mybers. You can require SSO for all team members so everyone authenticates through your provider.
SSO governs staff and admin access to your organization. Members continue to use the member portal login. SSO and required-SSO enforcement are available on higher plans.