Skip to content
API Cloud

API product

API Products allow Trimble Developers to package API Proxies into API Products based on value, making it easier for Consumers to access and consume a set of API Proxies for their use cases. Packaging of API Proxies also simplifies management of the underlying resources.

When you publish an API product, you must map API Proxies of the API. You can customize instances of the API Product with different rate limit conditions by applying custom policies. Because each API Product instance can include several API instances, and each API can be included in multiple API Products, the combination is limitless.

API product best practices

The following example will help you understand how an API Product can be best used to facilitate consumer engagement. Let’s assume a Telematics division enables customers to access results using the following APIs:

  • Map API
  • Location API
  • Weather Alarm API
  • Fuel Transaction API
  • Maintenance API
  • Routing and Dispatching API
  • Other Vehicle Location API

Appropriate APIs are actualized in an API Product so that consumers can make most out of subscribing to an API Product. Publishers can also package different APIs based on consumer requirements and scenarios.

Telematics BasicTelematics ProTelematics Advanced
- Map API
- Routing and Dispatching API		- Map API
- Location API
- Fuel Transaction
- Routing and Dispatching API		- Map API
- Location API
- Fuel Transaction
- Routing and Dispatching API
- Maintenance API
- Weather Alarm API
- Other Vehicle Location API