Your first integration
Open Quick start in the console, enter a product name, choose a language and run the downloaded bundle. Configuration is already filled in. Once the example works, adjust your license rules.
See the full steps →Use settings, error codes and request records to find the cause.
Open Quick start in the console, enter a product name, choose a language and run the downloaded bundle. Configuration is already filled in. Once the example works, adjust your license rules.
See the full steps →Check Usage and Balance in the console. API_BALANCE_INSUFFICIENT means insufficient funds for the next API charge; API_QUOTA_EXCEEDED means the period's call limit is reached.
Read billing rules →The cache is bound to this computer's system identity. Activate again on a new computer; release an old device if the limit is full. Long-term offline devices must reconnect to learn about revocation or new rules.
Read about device binding and limits →If the vendor linked your email to a license, a one-time login link lets you view licenses, release devices, get offline activation responses and view eligible releases.
Open the customer portal →Keep the request_id, error code, operation, timestamp and SDK language/version. Check usage and audit records in the workspace, then share these details with the platform or product administrator.
Support-page examples do not need passwords, full API keys or license keys.
Look up error codes →