Authentication Guide

Overview

After completing the technical onboarding process and receiving your clientID, clientSecret, and API base URL, you need to obtain a bearer token from Daimler Truck's BusinessID system to authenticate your API requests. This token must be included in the Authorization header of all API calls.

Prerequisites

• Valid clientID and clientSecret obtained during technical onboarding
• Access to Daimler Truck's BusinessID system
• Understanding of OAuth 2.0 authentication flows

Authentication Flows

Daimler Truck BusinessID supports OAUTH 2.0 client credentials flow.

Client Credentials Flow

This is the flow which is suitable for system-to-system communication use-cases.

Parameters

• Token Endpoint: https://login.ciam.daimlertruck.com/3db550f0-0c7f-439b-8e24-e32bf233615d/b2c_1a_signin_oidc_row/oauth2/v2.0/token
• Grant Type: client_credentials
• Scope: openid https://dtagapim.ciam.daimlertruck.com/DTAG_API/.default

Request Example

cURL Example

Token Response

After your request, you will get a JSON response containing the access token:

Token expiry: Check the expires_in property to see the token expiry time. You must refresh your token before it expires.

Using the Bearer Token

Include the bearer token in the Authorization header of your API requests:

 API Versioning

Depending on the API product, the version may be specified in different ways. Check the API documentation of the product you are using to determine which versioning method applies.

Path Versioning

The API version is included as part of the URL path.

Example:

Header Versioning

The API version is passed as a parameter in the request header.

Example:

Query Parameter Versioning

The API version is included as a query parameter in the request URL.

For additional details on which versioning method applies to a specific API product, please refer to the individual API documentation.

Error Handling

Common error responses:

Best Practices

1. Token Caching: Cache tokens and reuse them until expiration
2. Secure Storage: Store client credentials securely, never in client-side code
3. Token Refresh: Implement automatic token refresh before expiration
4. Error Handling: Implement proper error handling for authentication failures
5. HTTPS Only: Always use HTTPS for token requests

Next Steps

Once you have obtained your bearer token, you can start making authenticated requests to the available API products:

• Parts Information API: Access comprehensive parts data
• Vehicle Data Card API: Retrieve vehicle specifications and details

For specific API endpoints and usage examples, refer to the individual API documentation for each product.