--- order: 6 slug: "/docs/v1/start/glossary" title: "Glossary" section: "Start here" description: "Alphabetical definitions of every canonical KDPika Licensing term, from activation and credentials to products, signed state and webhooks." audience: "all" level: "beginner" last_updated: "2026-10-17" version: "v1" related: ["/docs/v1/start/core-concepts","/docs/v1/start/authentication"] draft: false --- Find the precise meaning of every canonical term used in KDPika Licensing documentation. ## What you will learn - Distinguish identifiers, secrets, records and platform billing terms. - Read the same vocabulary across guides and examples. ## Prerequisites - No account required. - Read the [core relationships](/docs/v1/start/core-concepts) for context. ## Alphabetical terms ### Activation Authorization of one installation and issuance of a token. Usage: Activation; seat count and lifetime count differ. ### Activation count Lifetime increments for new or inactive installation activation. Usage: Activation count; device reset does not clear it. ### Activation token act_ secret whose hashed row binds license/device. Usage: Activation token; never Public App ID. ### Active devices Number of ACTIVE device rows for a license. Usage: Active devices; does not drop on suspension alone. ### Customer Developer's software buyer/license recipient. Usage: Customer; platform customer must be explicitly qualified. ### Delivery Per-endpoint queued attempt series whd_ with at most6attempts. Usage: Delivery; not exactly-once business execution. ### Demo data Fictional dashboard/marketing example, not measured platform usage. Usage: Demo data; visible adjacent to the mock, with an accessible group label. ### Developer Software developer subscribing to KDPika Licensing. Usage: Developer; not the developer's software customer. ### Developer API key Product/environment-scoped lmp_ secret for trusted server management. Usage: Developer API key; never embed in distributed client. ### Device Server record binding a license to a hashed installation identity. Usage: Device; not guaranteed physical hardware uniqueness. ### Feature Named entitlement definition with boolean or typed JSON value. Usage: Feature / entitlement; feature value needs valid license guard. ### Idempotency key Organization-scoped create-request replay identity retained24h. Usage: Idempotency key; not a universal all-endpoints guarantee. ### Installation ID Persistent random identifier provided as device_id and X-Installation-ID. Usage: Installation ID; no hardware fingerprint requirement. ### KDPika Licensing Canonical product brand; a managed SaaS for software developers. Usage: Preserve code/package identifiers; KDPika is the company name and constrained short display. ### License Product/customer/environment entitlement record with lifecycle and limits. Usage: License noun; never a synonym for API key. ### License key Secret presented to activation; hashed/masked on license row but retained in idempotency response24h. Usage: License key; not activation token. ### Live Production license/customer/key/webhook environment, paid entitlement required. Usage: Live display; LIVE header; live payload; Stripe mode is separate TEST/LIVE. ### Official SDK Maintained Python/PHP/JavaScript/C# client, with currently logged conformance gaps. Usage: Official SDK; never imply flawless/fullOS verification. ### Offline grace Absolute signed offline_grace_until boundary used with expiry and validity checks. Usage: Offline grace; not permission to ignore server rejection. ### Organization Tenant/workspace owning products, customers, licenses and developer billing. Usage: Organization; Workspace is a UI label; not a buyer account. ### Platform Admin Operator with separately provisioned platform-admin privilege. Usage: Platform Admin; workspace Owner is not Platform Admin. ### Platform plan Free/Starter/Pro/Business capacity and billing tier for developer organization. Usage: Platform plan; EUR source is runtime platform_plans. ### Platform subscription Developer capacity/payment relationship with KDPika via Stripe or Mollie. Usage: Platform subscription; not software-buyer payment processing. ### Product Shared definition of a developer's application, public App ID and policy. Usage: Product; not Stripe Product or platform subscription plan. ### Product plan Developer-defined license template with price/duration/device/feature policy. Usage: Product plan; not platform plan. ### Public App ID Nonsecret app_ identifier used for activation via X-App-ID. Usage: Public App ID; reject secret App key wording. ### Public verification key Raw32byte Ed25519 key represented unpadded base64url. Usage: Public key; not webhook signing secret. ### Request ID req_ support correlation ID; replay body may retain original while header is current. Usage: Request ID; no secret. ### REST client example Transport example using the same API, not a full SDK. Usage: REST client; not official SDK for remaining10languages. ### Sandbox Separate test license/customer/key/webhook environment. Usage: Sandbox display; SANDBOX header; sandbox payload. ### Scope Registered action permission: licenses:read, licenses:write, devices:write. Usage: Scope; arbitrary string does not grant a new API. ### Signed envelope payload,signature,algorithm,key_id object using Ed25519. Usage: Signed envelope; outer HTTP success/token/request_id is unsigned. ### Source-confirmed Behavior inferred by reading exact source, not executed proof. Usage: Distinguish source-confirmed, locally reproduced and unverified hosting/provider facts. ### Validation interval Product hours until next normal online validation, measured from server_time. Usage: Validation interval; grace is not added after it. ### Webhook Optional signed outbound event to developer backend. Usage: Webhook; licensing validity never waits for recipient. ### Webhook event ID evt_ logical ID stable across retries/eligible recipient deliveries. Usage: Event ID; not delivery ID. ### Workspace role Organization membership OWNER/ADMIN/DEVELOPER/SUPPORT/VIEWER; actual route permissions must be checked. Usage: Role is not a paid plan or subscription badge. ## Expected result You can look up every term in the canonical terminology source and distinguish a customer license from your platform subscription. ## Common mistakes - Calling every credential a license key. - Confusing a workspace role with a subscription plan. - Assuming a hashed identifier is inherently anonymous. ## Security notes Examples of prefixes identify credential types; they are not usable secrets. Keep full activation tokens, license keys and developer API keys out of logs and feedback. ## Troubleshooting | Symptom | Cause | Fix | | --- | --- | --- | | Two names seem interchangeable | They describe different layers | Compare the definitions and core relationship diagram | | A term differs from a JSON member | Prose naming and code identifiers differ | Preserve the exact API or SDK member in code | | A scope name appears unfamiliar | Arbitrary scopes do not grant new endpoints | Use the registered scopes in authentication | ## Next steps Read [authentication](/docs/v1/start/authentication) or return to [core concepts](/docs/v1/start/core-concepts). ## Related - [Introduction](/docs/v1/start/introduction) - [Activation flow](/docs/v1/start/activation-validation-deactivation) - [Documentation home](/docs)