Automating Commercial Fleet Management

If you make frequent updates to which bikes you insure, you can automate these updates to your policy via Laka's API or by sending a .csv to an endpoint.

January 15, 2026

Both API and .CSV methods require the following fields:

• Unique Policy ID
  • Speak to your account manager to get this
  • Please note this is not the policy ref (P-123456)
• Product Type (Bicycle)
• Bike Frame Number / Serial Number
  • This will be the unique key of your product
• Bike Make (Brand), eg. Cannondale
• Bike Model
• Bike Value
• Bike Type eg. Cargo, Gravel, Folding
• eBikeType eg. assisted, pedelec, null
• Currency code (EUR or GBP)
• Bike Value in £ or Euro, no decimals
• Storage Address, split by:
  • Street Name
  • Postcode
  • City
  • Country (must be in ISO A-2 format) eg. GB or NL

Storage addresses are required for all product types.

Please note: Some commercial clients are exempt from providing a storage address. These are mainly clients who rent products for a day or two at a time, and do not store insured fleets at a single address. For example, a company like an AirBnB for bikes. If you are unsure, speak to your account manager.

Using the Laka API

Get in contact with your account manager who can provide your credentials.

You must make a separate request to the API for each policy you are adding or removing bikes from. Please view the requirements and support docs here.

Using a .CSV Endpoint

.csv endpoints are available to existing high-volume clients to assist with the migration from Google sheets to app.laka.co. Get in contact with your account manager who can provide the URL to send the .CSV to for ingestion.

Send the .csv which contains a series of instructions for adding, removing or patching (updating) bicycles to specific policies using the exact template below at the moment you want to update your policy.

Common scenarios:

1. Updating a bike value, type or location

   1. Use the PATCH Command

2. Moving a bike from one Policy to another

   1. The bike must be DELETED from Policy A, then CREATED on Policy B