Fleet Management API
Related Manuals
- Introduction to Fleet Complete API
- API User management
- API calls generic description
- API Customer management
- Vehicle management
Introduction to Fleet Complete API
API makes some of FCPlus features available for external applications. In order to start using API, you need API key. API key is a secret token that can be assigned to a user record to authorize your calls to Fleet Complete system. Calls authorized via API key have all rights inherited from the user the key is attatched to. Please consider that while managing the access rights you give to your API user.
Please read this article, how to get and manage rights for such API key.
Fleet Complete API
FCPlus has two endpoints, depending on in what server your account is hosted. Official API page are in addresses:
-
For customers with accounts in server for Nordic and Baltic countries https://app.ecofleet.com/seeme/services/apidoc
-
For customers with accounts in server for Benelux/Germany/Greece: https://eu.ecofleet.com/services/apidoc/
It is user interface, what lists all available API calls, and allows to test them with your existing API user. You can play with various parameters there.
API guide is just user interface for actual API calls. In your real application, you have to call API commands with direct API links, and pass correct GET parameters.
There are following direct API addresses in use, depending on what server are you using:
Start every call with that endpoint. In this guide, we're using first one, but replace it with other one, if your account is in different server.
All API calls contains at least one parameter key, what passes API key. For example, this test call:
app.ecofleet.com/seeme/Api/Vehicles/get?key=yourApiKey eu.ecofleet.com/Api/Vehicles/get?key=yourApiKey
Lists all vehicles, what are shared out to API user.
All API responses have same generic response:
<?xml version="1.0" encoding="utf-8" ?>
<nodes>
<status>query status</status>
<response>query data</response>
<errormessage>some error message</errormessage>
</nodes>
Here:
- status shows, was query successful or not. All nonzero values show problem
- message contains useful data for that API call
- errormessage, if exists, contains error message about why query was unsuccessful.
See some deep analysis, how to handle and manipulate API calls, here.
Some API calls are so advanced, that they must be covered separately. Other articles under that section help you out to get working some advanced commands.
Carsharing API
There is separate API for Carsharing/Vehicle booking solution.
This API described in YAML file