Trimble Credits APIs

EMS Session Creation API

POST /v3/sessions/create

EMS Session Service

The EMS Session Service is responsible for issuing signed session tokens (JWTs) that applications use to enforce usage-based entitlements. It acts as the bridge between Trimble Identity (TID) and downstream applications by converting an authenticated TID access token into a purpose-built session token containing the account’s billable metric context.

What it does

When a client application starts a session, it sends its TID access token along with the desired features to this service. The service extracts the caller’s identity from the TID token, looks up the relevant billable metrics for the requested features, and issues a short-lived RS256-signed JWT. This session token is then passed to the application, which can use it to track usage against the correct billing metrics without needing direct access to the metering backend.

The service also exposes a public JWKS endpoint so any downstream consumer can independently verify session tokens using standard JWT libraries — no shared secrets required.

Key capabilities

• Issues RS256-signed session JWTs with 24-hours expiry.
• Extracts application identity from incoming TID tokens automatically.
• Maps requested features to billable metrics from an internal configuration store.
• Provides a public JWKS endpoint for decentralized token verification.
• Follows the RFC 7807 error format for all error responses.

Endpoints

• POST /v3/sessions/create — create a session token (requires TID bearer token).
• GET /v3/keys/jwks — public key set for token verification.

Reference: EMS Session Service.

Ingest Usage Event API

POST /v1/usage/events

• Create an EMS session using POST /v3/sessions/create.
• API specification: Ingest Usage.
• Steps to generate an application access token — see the source onboarding document.
• API flow sequence: Lucid chart.
• As long as the EMS Session token remains valid, ingestion is permitted.

Get Account Balance API

GET /v1/accounts/{accountId}/balance

• API specification: Get Account Usage.
• Steps to generate an application access token — see the source onboarding document.
• API flow sequence: Lucid chart.

Note

If the integrating application is EMS V4 compliant and has an active license ID, the application should fetch the CDH account ID corresponding to the license ID from EMS V4, and then invoke the net balance API.