Develop

How-to guides for developers integrating MonetizeIt into an application or device.

• Authentication — the two credential models: client credentials for your backend, activation code + fingerprint for the runtime — and which endpoints take which.
• .NET SDK — install and configure the license consumer, then follow the series: activate, enforce entitlements, report usage, work offline and fingerprint devices.
• Using the REST API — URL areas, pagination, update semantics, retries and the error contract; call everything directly in any language.
• Offline (air-gapped) activation — activate and keep licensed machines that never connect, via signed files.
• Receiving webhooks — verify signatures, answer the registration challenge, survive retries and secret rotation.

Tip

A client SDK is a convenience wrapper around the REST API — it does nothing you can’t do over REST. A C++ client with a C-callable wrapper is available for native applications, and any language with an HTTP client and a JWT library can implement the same loop: activate, cache, validate, report. The API is the full contract.