Integrations

Oclavex is the licensing side of your stack: it owns entitlements, activations and usage. Your CRM and billing tools own accounts, deals and charging. An integration keeps the two in sync — a subscription starts in your billing tool, an entitlement appears in Oclavex; a device activates in Oclavex, the account in your CRM shows it.

Everything here is built on two primitives you already have, so there is no special SDK to adopt:

You want	You use
React when something happens in Oclavex	Outbound webhooks — signed events to any HTTPS endpoint
Drive Oclavex from another system	The REST API with per-integration credentials

The integrations

Integration	What it does	Status
Zapier	Trigger Zaps from Oclavex events, and let Zaps call back into the API	Available (generic webhooks — nothing to install)
Stripe	Subscriptions create, pause and end entitlements; checkout from inside your application	Available (connector on Evaluation, Professional and Enterprise; a relay you wire yourself on any plan)
Your own billing system	Post subscription, account and credit events from any billing system; Oclavex applies them as it does Stripe’s	Available (Evaluation, Professional and Enterprise)
Salesforce	Two-way sync: accounts, contacts and orders in; license state projected back onto Salesforce records	Preview (Evaluation and Enterprise)

Where Oclavex stops

Oclavex does not charge cards, send invoices or run dunning — that stays with your billing provider. What crosses the boundary is events: a billing or CRM change tells Oclavex to create, pause, resume or cancel an entitlement; a licensing change tells your other tools that a customer activated, is nearing a quota, or let a trial lapse. Each side keeps doing what it is best at.

Because the contract is source-agnostic, the same pattern that connects Stripe also connects any other billing or subscription tool: billing events take the events the Stripe connector produces straight from your own system. The integration pages are worked examples, not the only options.