Fuse API

 

This table provides the event and query domains for the primary service modules that make up the overall Fuse system. There is a development and a production domain. 

Production

Domain

Development

Domain

Ruleset
Name 
Description
b16x9v1_fuse_vehiclefuse_vehicle.krlServices for the overall vehicle Pico
b16x10v1_fuse_keysfuse_keys.krlKeys for various APIs (protected)
b16x11v1_fuse_carvoyantfuse_carvoyant_mashery.krlServices for interacting with Carvoyant API
b16x13v1_fuse_errorfuse_error.krlServices for handling error events
b16x16v1_fuse_ownerfuse_init.krlServices for the owner pico
b16x17v1_fuse_fleetfuse_fleet.krlServices for managing the fleet
b16x18v1_fuse_tripsfuse_trips.krlSeries for Trips API
b16x19v1_fuse_commonfuse_common.krlCommon functions; used by most Fuse rulesets
b16x20v1_fuse_fuelfuse_fuel.krlServices for the Fuel API
b16x21v1_fuse_maintenancefuse_maintenance.krlServices for the Maintenance API
b16x22v1_fuse_bootstrapfuse_bootstrap.krlService for bootstrapping a new Fuse account
b16x23v1_fuse_fleet_oauthfuse_fleet_oauth.krlServices for managing OAuth between the fleet pico and Carvoyant
b16x26v1_fuse_reportsfuse_reports.krlFunctions for creating reports (no need to be installed)

 

The structure of the Fuse API follows the pico structure

Todo

Registering as a Developer

OAuth2/Delegated Access