License Enforcement
EMSv4 provides the source of truth for Trimble User (or Device) license assignments. Trimble products are responsible for consuming this data to perform license enforcement within their product or system boundaries.
License enforcement within Trimble products involves two steps:
- Requesting an
access_tokenthat authorizes a client application to retrieve licensing information for TID Users or Devices. - Using that
access_tokento execute a GET request to the EMSv4/licensesendpoint, which will return a paginated list of licenses for the Trimble Users, Devices, or Applications specified by the request. Trimble products use these returned licenses to authorize access to its features and capabilities.
The /licenses endpoint supports many combinations of query parameters and TID identity types. The most request pattern filters licenses using the sku, featureId,accountId, and status query parameters. Products should use the most restrictive set of query parameters applicable to their use case to minimize the size of the response.
Trimble products that use Trimble Access Management (TAM) for data authorization can optionally perform EMSv4 license checks directly within the TAM environment using the trimble.entitlement.licenses package. This enhances your EMS v4 integration by enabling license caching and pagination on the product’s behalf