API keys and webhooks

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 change, events are created or published, programs change status, or an event registration is confirmed. All payloads are signed with HMAC-SHA256. Each event is delivered once, with no automatic retry.

Automation tools (Zapier, Make, n8n, Custom Webhooks)

The automation cards in Settings → Integrations are the easier route for most orgs: paste the catch-hook URL from Zapier, Make or n8n (or your own HTTPS endpoint under Custom Webhooks) and Mybers posts each change as it happens: member.created, member.updated, member.lapsed, payment.received, event.published and the rest. Custom Webhooks signs the body with your secret (X-Mybers-Signature) and retries twice, after 1 and 3 seconds, when your endpoint is down or returns a server error. The Overview tab shows the last delivery and the last failure.

Social pages (Facebook, LinkedIn)

Connect a Facebook Page or LinkedIn company page and each event posts once when you publish it, with the date, place and a link to the event page. Turn on the cancellation follow-up on the Triggers tab if you want one. Every post appears in the Logs tab.

REST API

See the full API Reference in Settings → API → Docs for endpoints, rate limits, pagination, and example curl commands.