Need subscription data in your CRM? Member updates in your mailing tool? Triggers for your own app? Via the REST API you pull whatever you need — via webhooks we push events to you live.
Members, subscriptions, payments, invoices, plans — everything fetchable via REST. JSON in, JSON out.
Payment success, subscription cancel, member join, refund — all pushable as webhooks. With HMAC signature for authenticity checks.
Per community you create multiple API keys, each with its own read/write scopes. Your Zapier key stays separate from your custom-dev key.
The JoinOurServer API strictly follows REST: predictable URLs (/api/v1/members, /api/v1/subscriptions/:id), HTTP verbs for actions, JSON bodies. Auth via bearer token in the Authorization header.
Full OpenAPI spec with examples is in the API docs — you can fire test calls straight from there.
For every relevant lifecycle event (new payment, subscription cancel, refund, member join, member leave) we POST to your configured URL. The body contains the event with all context data — directly usable in Zapier, Make.com, n8n or your own backend.
Every webhook is signed (HMAC-SHA256) — you can verify authenticity without having to trust us. On receive failure (5xx response from you) we retry with exponential backoff.
Default: 60 requests per minute per API key. For higher limits, contact us. Webhooks have no rate limit (you receive, we send).
Not yet — but the API is designed so you can start in any HTTP-capable language (PHP, Python, Node, Go, Bash) in 5 lines. Examples in the docs.
Yes. In the dashboard there's a "Send test webhook" button with sample payloads per event type. Locally you can use ngrok or webhook.site.
OpenAPI spec with runnable examples — from member listings to webhook subscriptions.
Start for freeWe use cookies and similar technologies to operate the platform and to analyse its usage. "Necessary" cookies are technically required (login, session, CSRF). Statistics and marketing cookies are only activated if you consent. More info: privacy policy.
Session, login, CSRF protection. These cookies are required to operate the site and cannot be disabled.
Anonymised usage data (page views, browser, approximate location) for improving the platform. ID: G-K1B9Z8G1ZC.
Tag Manager for dynamic loading of advertising pixels and conversion tracking. ID: GTM-54M9WF9Z.