FAQs
Situation: A customer is using a fleet management app to track their machines, but suddenly, the data stops updating. They report the issue to their app system support team.
Investigation: The support team checks the issue and notices that
- The machines are still sending data (machine communication is working).
- The app is receiving 403 Forbidden errors when trying to fetch data from the Volvo API.
What should the customer do next?
Verify API authentication details and contact the Dealer Support Center (DSC) if needed.
Situation: A customer notices that their fleet dashboard is displaying incorrect fuel levels for multiple machines. Some machines are showing as empty, even though they were recently refueled.
Investigation: The customer cross-checks machine data and finds
- The API is responding normally with no errors.
- The issue affects only specific machines, not all.
- When checked manually, the machines have fuel, but the reported fuel level is incorrect.
What should the customer do next?
Contact the dealership for Machine Support. If further investigation is required, the issue can be escalated through a CHAIN case by the dealership.
Both AEMP 2.0 and the Extended Asset API have defined rate limits and burst limits, which vary depending on the selected subscription plan (Base or Advanced). Each plan specifies the maximum number of requests that can be made within a given time period.
Detailed information about the available plans, rate limits, and usage guidelines can be found in the product documentation and the developer portal once access has been granted and you have logged in.
Go to your application page to see the number of requests made by your application for different APIs.
Click ‘Apps’ in the main menu, then select your application.
In the ‘Product Subscriptions’ table, you’ll find all the plans your application is subscribed to.
For each API in the plan, you can view the usage compared to the plan’s rate limit.



When you create an application you are provided with an API Key and Secret for the application. You must supply these credentials when you call an API that requires you to authenticate your application.
To register an application click on Apps in the main menu and then click on the 'Create new app' link. Once you have provided an application name, description, etc you will be shown your application API Key and Secret.
Make a note of your API Secret because it is only displayed once.
More information can be found on the GET STARTED page.
Your API Secret is stored encrypted, so we cannot retrieve the unencrypted version to tell you the value if you forget it.
You can reset it, which will update the stored value and return the new value to you.
To do that, click 'Apps' in the main menu, click on the application in question, and then you can click the 'Reset' link in the 'API Secret' section.
Your new Secret will be displayed at the top of the page.
All new customer orders for the AEMP2.0 API as well as the Extended Asset API will be processed through the Services Marketplace (SMP) by the dealership.
For Key Accounts, the existing ordering process using the API Product Order Form will remain unchanged.
API subscriptions are linked with the Connected Services offering of CareTrack Start and CareTrack Advanced. Before ordering, dealers must secure acceptance of the Connectivity Terms & Conditions and the Data Management Agreement with the customers.
The onboarding process of the customers will continue to be managed by the Volvo CE Commercial Integration Framework (VCIF) support team upon order confirmation, following the existing process as described on the Commercial Services Developer Portal.
Feature / Need | AEMP 2.0 | Extended Asset API |
|---|---|---|
Primary Purpose | Standardized, ISO 15143-3 telematics for mixed fleets | Extended with more Volvo-specific machine insights (diesel + electric) |
Best For | Customers needing basic telematics in a common format across multiple OEMs | Customers needing richer data fields, electric machine insights, or custom integrations |
Fleet Type | Ideal for mixed fleets using third-party systems | Ideal for Volvo-heavy fleets, electric fleets, or custom-built solutions |
Data Depth | Essential fields: location, hours, utilization, fuel use, ISO standard fault codes. | Extended fields: battery status, charging, energy consumption, fault codes (including from older generation machines). |
Electric Machine Support | Limited | Full support (battery, charging, energy data) |
Diagnostic Data | Basic ISO 15143-3 standard | Includes Volvo fault/error codes and advanced diagnostics |
Format | ISO-defined structure | Flexible JSON schema |
Call Rate | Standard | Higher limits for near real-time integrations |
Customization | Limited; fixed ISO standard | Highly flexible; supports tailored data consumption |
Future-readiness | Stable baseline | Built to expand with new technologies and data schemas |
Typical Use Case | Third-party fleet platforms | In-house systems, advanced analytics, predictive maintenance |