> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/common-scenarios/glossary/general.md). # General ### Reseller and Distributor Portals The distribution portal refers to a comprehensive set of functionalities that empower vendors to enhance their existing License Managers by incorporating distribution capabilities. This enables vendors to assume the role of distributors themselves. With this feature, vendors gain the ability to create and manage their own orders, as well as add licenses to these orders, without relying on direct involvement from the software vendor. The reseller portal grants license managers the ability to issue licenses within assigned orders while restricting them from creating new orders. For more information, see [**Reseller \_ Distributor Portals**](/license-entitlements/portal/end-user-portal/reseller-_-distributor-portals.md). ### HardwareID Also known as device ID, instance ID, or device fingerprint, the [**Hardware ID**](/sdks/tutorials/best-practices/hardware-id-generation.md) is a hash generated by our SDKs during license activation. It combines various hardware components of a computer, such as the hard disk drive and CPU. The Hardware ID serves as a unique identifier for the computer, allowing it to be tracked against the maximum number of activations. If an end user attempts to activate the license on a new machine, it will consume an additional activation from the license. In some cases, developers can override the computation of the Hardware ID if they have their own means of identifying the end user or use a custom device fingerprinting algorithm. ### License API The [**License API**](/license-api/introduction.md) is specifically designed to be accessed by clients, allowing them to activate, deactivate, and check the status of licenses for a particular software or service. ### License API Key and Shared Key The License API Key is your company's unique API key used for integration purposes. You can find this key in the "SDK integration" section of your product. The shared key is a company-specific encryption key utilized for signing requests. It ensures secure communication between entities. You can find this key in the "SDK integration" section of your product. More information about locating the License API and Shared Key and connecting to the API can be found in [**SDK tutorials: Getting Started**](/sdks/tutorials/getting-started.md). ![License API and Shared Key Locations](/files/7d4301076bde810c63c5973ba93ee00654f08cf7) ### LicenseSpring Vendor Platform LicenseSpring's [**Vendor Platform**](/vendor-platform/platform.md) enables users (your staff members) to securely log in and efficiently manage the organization's licenses. ### Management API The [**Management API**](/management-api/introduction.md) is intended for organizations to manage and modify existing license entitlements and orders. These APIs possess powerful capabilities and should not be exposed directly to clients or included in client applications. ### User Portal The [**End User Portal**](/license-entitlements/portal/end-user-portal.md) allows users to access license information, perform self-service actions, and manage their licenses efficiently. ![End-User Portal](/files/c5a0c636a9141c12d65e1c2e75873cde086e8643) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.licensespring.com/common-scenarios/glossary/general.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.