First API call
In 2 minutes: create an API Key and make your first authenticated request. Ideal for scripts and server-to-server integrations.
Sign in with Cativa
In 5 minutes: let Cativa users log into your app via OAuth 2.0 with PKCE.
What you can build
- Two-way CRM sync (HubSpot, RD Station, Pipedrive)
- Access provisioning from external purchase (Hotmart, Kiwify, Eduzz, Shopify)
- No-code connectors (Zapier, Make.com, ActiveCampaign)
- AI agents via MCP (coming soon)
Two ways to authenticate
Before you pick an endpoint, pick how you’ll authenticate. The rule is simple:API Key (server-to-server)
Your application acts as itself. Send
Authorization: Bearer cativa_live_.... Use it in jobs, syncs, and backends with no interactive user.OAuth 2.0 + PKCE (on behalf of a user)
The end user authenticates with their community account. Use it when you need the user’s identity in your app.
Core concepts
Read these before diving in. Each one explains a building block of the platform you’ll meet in the endpoints and webhooks.Tenants and Customers
What a tenant is, how
customerName shows up in integrations, and why IDs are unique per community.Identity and Users
The user model: profile, normalized email, E.164 phone, and the account lifecycle.
Badges as Permissions
How badges gate access to groups and courses. In Cativa, a badge is a permission.
Communities and Spaces
Groups, spaces, and how content is organized inside a tenant.
Posts and Comments
The community feed: posts, comments, and how they connect to groups.
Events
Live and scheduled events, Zoom integration, and the attendance lifecycle.
Courses and Certificates
Courses, lessons, progress, and certificate issuance.
Store and Coins
The internal economy: coins, the wallet, and the community store.
Payment Links and Subscriptions
Paywalls, checkout, and what happens when a payment is confirmed.
Segmentation and Funnels
How to segment users and trigger automations from their behavior.
Receive events with Webhooks
Instead of polling the API every minute, let Cativa notify you when something happens. Webhooks deliver events likeuser_created, user_received_badge, and paywall_payment_completed to your endpoint, signed with HMAC.
Webhooks (overview)
Why webhooks, delivery guarantees, HMAC signing, and retries.
Subscribe and verify
The step-by-step: register a listener, verify the signature, and handle idempotency.
Practical guides
Implement Sign in with Cativa
The deep SSO guide: SPA, backend, and mobile, with
id_token validation via JWKS.Grant access via purchase
Wire the external purchase flow that provisions access in the community.
Sync members from a CRM
Keep users in sync between your CRM and Cativa.
Federated login
Connect Cativa to an identity provider you already run.
Need help?
Support
Send an email with an example request and the
traceId returned in the error body. We reply within 1 business day.