Developer path

Embed Oclavex in your app with a client SDK. Three steps take you from nothing to an enforced feature and reported usage.

Prerequisite: a published entitlement with an activation code to activate against. If nobody has set one up yet, run the Admin path (portal) or the API quickstart first — it takes a few minutes.

Steps

1. Add and configure the client SDK — install Revenusion.MonetizeIt.Client.LicenseConsumer (plus Revenusion.MonetizeIt.Client.AspNetCore for host apps) and point it at your tenant.
2. Activate a license — call the SDK’s activate method with an activation code and device fingerprint; it returns a session your app holds for the rest of its run. Activation is anonymous, so a shipped app needs no API credentials of its own.
3. Gate a feature and report usage — check is this allowed? before a gated feature, then report what’s consumed.

Unattended backends

An app whose entitlement requires an authenticated activator — an unattended backend or appliance with no interactive user — activates with OAuth client credentials instead of an anonymous code. Create a client under API Credentials — every plan includes at least one client credential (Oclavex Plans) — then see configuring the SDK.

Tip

A client SDK is a convenience wrapper — everything it does is on the REST API, so any language works. To see the exact calls, run the API quickstart.

Step-by-step .NET guides start at Install and configure the SDK; the full set lives under Develop.