Client Credentials

The Client Credentials grant type is used by clients to obtain an access token outside of the context of a user. The client application is assumed to be the resource owner and the access request is to the application’s resources.

Important

An application access token should only be used in server to server calls and should not be used when making calls from a client-side application.

How It Works

The following diagram describes the Client Credential flow:

What You Need

You will need the following information from Trimble:

• Client ID
• Client secret

Credentials

This documentation refers to credentials. Credentials are Base64 encoding your combined Client ID and Client secret separated by a colon, e.g.: Base64(id:secret).

Token

Request

POST /oauth/token

Header

Header	Description
Authorization	Basic credentials
Content-Type	application/x-www-form-urlencoded

Body

Body is x-www-form-urlencoded with the following fields:

Field	Description
grant_type	client_credentials
scope	Include only the scope(s) needed to enable intended functionality as documented for each API product to which access is being granted.

Examples

The following are examples of token requests using the Client Credentials grant type.

HTTP

POST /oauth/token HTTP/1.1
Host: id.trimble.com
Content-Type: application/x-www-form-urlencoded
Authorization: Basic {credentials}
Content-Length: 89

grant_type=client_credentials&scope={scope}

cURL

CURL

# Application credentials
client_id="client ID"
client_secret="client secret"

encoded_credentials=$(echo -n "$client_id:$client_secret" | base64)

curl --location "https://id.trimble.com/oauth/token" \
--header "Content-Type: application/x-www-form-urlencoded" \
--header "Authorization: Basic $encoded_credentials" \
--data-urlencode "grant_type=client_credentials" \
--data-urlencode "scope=$scope"

Response

{
  "token_type": "bearer",
  "expires_in": 3600,
  "access_token": "eyJhbGciOiJ...LaHpfIpRAzHakV2ossbnpA"
}