# Api Login Source: https://docs.ctechnology.io/api-reference/account/api-login /api-reference/openapi.yml post /account/login Log a user in. # Api Logout Source: https://docs.ctechnology.io/api-reference/account/api-logout /api-reference/openapi.yml post /account/logout Log a user out. # Api Logout All Source: https://docs.ctechnology.io/api-reference/account/api-logout-all /api-reference/openapi.yml post /account/logout-all Log a user out of all sessions. # Get news articles Source: https://docs.ctechnology.io/api-reference/ecosystem/get-news-articles /api-reference/openapi.yml get /ecosystem/updates/news-article Gets all news articles available to a user. # Get all vehicle summaries Source: https://docs.ctechnology.io/api-reference/insight/get-all-vehicle-summaries /api-reference/openapi.yml get /vehicle/summary Returns the summaries of all vehicles with the given requirements. # Get overall summary Source: https://docs.ctechnology.io/api-reference/insight/get-overall-summary /api-reference/openapi.yml get /vehicle/{vehicle_id}/summary/overall Returns the overall summary of the vehicle. This summarizes everything since the vehicle / IoT device was put into service and adds some other interesting information. # Get vehicle summary of today Source: https://docs.ctechnology.io/api-reference/insight/get-vehicle-summary-of-today /api-reference/openapi.yml get /vehicle/{vehicle_id}/summary/today Returns the daily summary of the vehicle for today. # REST API introduction Source: https://docs.ctechnology.io/api-reference/introduction Introduction to the c.technology vehicle REST API ## Welcome to the c.technology REST API The c.technology vehicle REST API provides the ability to programmatically manage and interact with the full range of c.technology products and services. This includes managing vehicles, trips, notifications, maintenance schedules, and much more. > [!NOTE] > > Please reach out to us for access to OEM-specific fields and endpoints. > This documentation focuses on the general-purpose API used by self-service and standard customers. ## Key features * **Vehicle management**: Get and update vehicle profiles, monitor status, and retrieve action logs * **Trip tracking**: Access trip data, triplegs, and manage trip records * **Authentication**: Token-based authentication with personal or programmatic access tokens * **Comprehensive data**: Access to notifications, maintenance, insights, and more * **Real-time updates**: Many endpoints have real-time counterparts via the [AsyncAPI](/asyncapi-reference/introduction) ## API Version The c.technology API is versioned with the version identifier as part of the URL: ``` https://api.ctechnology.io/api/v2.2/... ``` The current version is `v2.2.0`. You can use `v2.2` without the patch version, as the API is backwards-compatible between patch versions. ## Authentication Most endpoints require authentication using access tokens. Include your token in the HTTP `Authorization` header: ``` Authorization: Token {your_token} ``` You can obtain a personal access token via the login endpoint, or create a programmatic access token from your admin panel. ## Request & Response Format Standard communication is done using JSON with an `application/json` content type. Responses always are of the following structure: ```json theme={null} { "header": { "api_version": "v2.2", "status": "SUCCESS", "message": "...", // Important for errors ... }, "data": { ... } } ``` Datetime fields use ISO 8601 format in UTC: `YYYY-MM-DDThh:mm:ss.sssZ` ## Rate Limiting Rate limiting is in place and depend on individual endpoints. If you receive a `429 Too Many Requests` response, check the `Retry-After` header for when you can retry your request. For push-based data updates without rate limits, consider using the [AsyncAPI](/asyncapi-reference/introduction) or webhooks. # Add notification rule Source: https://docs.ctechnology.io/api-reference/notification/add-notification-rule /api-reference/openapi.yml post /notification/rule/{vehicle_id} Add a new notification rule for the given vehicle (and logged in user). # Delete notification rule Source: https://docs.ctechnology.io/api-reference/notification/delete-notification-rule /api-reference/openapi.yml delete /notification/rule/{vehicle_id}/{notification_rule_id} Delete the given notification rule. # Get all notification rules Source: https://docs.ctechnology.io/api-reference/notification/get-all-notification-rules /api-reference/openapi.yml get /notification/rule Gets all notification rules for the currently logged in user. # Get all notifications Source: https://docs.ctechnology.io/api-reference/notification/get-all-notifications /api-reference/openapi.yml get /notification/alert Gets all notifications for the currently logged in user. This can include read and unread notifications, notifications after or before a given date/time, etc. Notifications are always returned sorted by timestamp, with the newest notification first. # Get notification Source: https://docs.ctechnology.io/api-reference/notification/get-notification /api-reference/openapi.yml get /notification/alert/{notification_id} Gets a single notification for the currently logged in user. # Get notification rules Source: https://docs.ctechnology.io/api-reference/notification/get-notification-rules /api-reference/openapi.yml get /notification/rule/{vehicle_id} Gets all notification rules for the currently logged in user and the chosen vehicle. # Update notification Source: https://docs.ctechnology.io/api-reference/notification/update-notification /api-reference/openapi.yml put /notification/alert/{notification_id} Update a single notification. # Subscriptions Get Source: https://docs.ctechnology.io/api-reference/payment/subscriptions-get /api-reference/openapi.yml get /payment/subscription [DEPRECATED] Use /payment/service-subscriptions/ instead. # Connect to vehicle Source: https://docs.ctechnology.io/api-reference/security/connect-to-vehicle /api-reference/openapi.yml post /me/connected-vehicle Connects a vehicle to the logged in user. You can choose a role which determines the access the user will have to the vehicle. Note that connecting might not always be possible but is restricted by previous assignments and access rights. # Create HTTP receiver auth token Source: https://docs.ctechnology.io/api-reference/security/create-http-receiver-auth-token /api-reference/openapi.yml get /security/vehicle/{vehicle_id}/vehicle-data-upload-token Creates an auth token that is used to auth update requests to the HTTP receiver endpoint. # Create vehicle access Source: https://docs.ctechnology.io/api-reference/security/create-vehicle-access /api-reference/openapi.yml post /permission/vehicle-access Creates a vehicle access (invites a user to access a vehicle). # Delete the vehicle connection Source: https://docs.ctechnology.io/api-reference/security/delete-the-vehicle-connection /api-reference/openapi.yml delete /me/connected-vehicle/{vehicle_id} Deletes an existing vehicle connection (between a vehicle and a user). This does not change the user nor the vehicle itself. # Delete vehicle access Source: https://docs.ctechnology.io/api-reference/security/delete-vehicle-access /api-reference/openapi.yml delete /permission/vehicle-access/{vehicle_access_id} Deletes a vehicle access. # Get user permissions Source: https://docs.ctechnology.io/api-reference/security/get-user-permissions /api-reference/openapi.yml get /permission Gets a user's permissions with respect to UI and general functionality. # Get user vehicle permissions Source: https://docs.ctechnology.io/api-reference/security/get-user-vehicle-permissions /api-reference/openapi.yml get /permission/vehicle/{vehicle_id} Gets a user's permissions for a single vehicle (that this user has access to). These permissions might vary from vehicle to vehicle (e.g., depending on if the user is the owner, maintainer or manufacturer of a vehicle). # Update vehicle access Source: https://docs.ctechnology.io/api-reference/security/update-vehicle-access /api-reference/openapi.yml put /permission/vehicle-access/{vehicle_access_id} Updates a vehicle access. # Delete a trip Source: https://docs.ctechnology.io/api-reference/trip/delete-a-trip /api-reference/openapi.yml delete /trip/{trip_id} Deletes a trip. # Get trip Source: https://docs.ctechnology.io/api-reference/trip/get-trip /api-reference/openapi.yml get /trip/{trip_id} Gets a single trip as identified by its ID. # Get tripleg Source: https://docs.ctechnology.io/api-reference/trip/get-tripleg /api-reference/openapi.yml get /tripleg/{tripleg_id} Gets a single tripleg as identified by its ID. # Get triplegs Source: https://docs.ctechnology.io/api-reference/trip/get-triplegs /api-reference/openapi.yml get /tripleg Gets triplegs that a user has access to. The triplegs are always ordered by their ending timestamp, newest one first. Use a `limit` query parameter to bound the number of trips returned. A tripleg is a part of a trip (between two staypoints). # Get trips Source: https://docs.ctechnology.io/api-reference/trip/get-trips /api-reference/openapi.yml get /trip Gets trips that a user has access to. The trips are always ordered by their ending timestamp, newest one first. Use a `limit` query parameter to bound the number of trips returned. # Get vehicle triplegs Source: https://docs.ctechnology.io/api-reference/trip/get-vehicle-triplegs /api-reference/openapi.yml get /vehicle/{vehicle_id}/tripleg Gets triplegs of the indicated vehicle. The triplegs are always ordered by their ending timestamp, newest one first. Use a `limit` query parameter to bound the number of trips returned. A tripleg is a part of a trip (between two staypoints). # Get vehicle trips Source: https://docs.ctechnology.io/api-reference/trip/get-vehicle-trips /api-reference/openapi.yml get /vehicle/{vehicle_id}/trip Gets trips of the indicated vehicle. The trips are always ordered by their ending timestamp, newest one first. Use a `limit` query parameter to bound the number of trips returned. # Update trip Source: https://docs.ctechnology.io/api-reference/trip/update-trip /api-reference/openapi.yml put /trip/{trip_id} Update a trip (setting its name, driver, etc.). # Get user profile Source: https://docs.ctechnology.io/api-reference/user/get-user-profile /api-reference/openapi.yml get /me Gets the profile of the currently logged in user (as indicated by the auth token). # Get user profile by ID or email Source: https://docs.ctechnology.io/api-reference/user/get-user-profile-by-id-or-email /api-reference/openapi.yml get /user/{user_id_or_email} Gets the profile of a user by either his / her user ID or email address. # Update user profile Source: https://docs.ctechnology.io/api-reference/user/update-user-profile /api-reference/openapi.yml put /me Updates information in the profile of the currently logged in user. Note that all fields are optional, i.e., a partial view of the request body may be given. # Send command to vehicle Source: https://docs.ctechnology.io/api-reference/vehicle-communication/send-command-to-vehicle /api-reference/openapi.yml post /vehicle/{vehicle_id}/command **Experimental**: Please be aware that using this endpoint migth require you to update your integrations at a later point in time. By sending commands to a vehicle you can either control the IoT devices' digital out pins (where you can connect arbitrary on-off things, or also any of our first-class supported devices), or send commands directly into a CAN / OBD2 / NMEA2000 bus. Note that by default only low-priority commands are supported. If you need high-priority commands (delivered immediately), please [contact us](https://ctechnology.io/contact). # Get a vehicle's actions Source: https://docs.ctechnology.io/api-reference/vehicle/get-a-vehicles-actions /api-reference/openapi.yml get /vehicle/{vehicle_id}/action Get a vehicle's actions. Actions are "things of interest" that happen with the vehicle, such as errors generated by the engine, entering/leaving harbor/home locations, exceeding speed limits, etc. Most actions are generated independent of a user's settings, but some are dependent on user choices (e.g., notification rules). In this case, the action contains a user ID for which it is valid, and the action is *not* reported for other users. The returned actions are sorted newest-first. # Get all vehicle profiles Source: https://docs.ctechnology.io/api-reference/vehicle/get-all-vehicle-profiles /api-reference/openapi.yml get /vehicle Get all vehicle profiles this user has (full) access to. # Get all vehicle statuses Source: https://docs.ctechnology.io/api-reference/vehicle/get-all-vehicle-statuses /api-reference/openapi.yml get /vehicle/status Gets all vehicles' current statuses, meaning their most up-to-date information such as location, battery state, motor state, etc. # Get vehicle actions Source: https://docs.ctechnology.io/api-reference/vehicle/get-vehicle-actions /api-reference/openapi.yml get /vehicle/action Get actions of all vehicles. Actions are "things of interest" that happen with the vehicle, such as errors generated by the engine, entering/leaving harbor/home locations, exceeding speed limits, etc. Most actions are generated independent of a user's settings, but some are dependent on user choices (e.g., notification rules). In this case, the action contains a user ID for which it is valid, and the action is *not* reported for other users. The returned actions are sorted newest-first. # Get vehicle profile Source: https://docs.ctechnology.io/api-reference/vehicle/get-vehicle-profile /api-reference/openapi.yml get /vehicle/{vehicle_id} Gets the given vehicle's profile. This consists of user-defined settings and profile information, as well as information about the hardware that is installed on the vehicle and its configuration. # Get vehicle status Source: https://docs.ctechnology.io/api-reference/vehicle/get-vehicle-status /api-reference/openapi.yml get /vehicle/{vehicle_id}/status Get a vehicle's current status, meaning its most up-to-date information such as location, battery state, motor state, etc. # Update vehicle profile Source: https://docs.ctechnology.io/api-reference/vehicle/update-vehicle-profile /api-reference/openapi.yml put /vehicle/{vehicle_id} Updates information in the specified vehicle profile. Note that all fields are optional, i.e., a partial view of the request body may be given. # Auth Source: https://docs.ctechnology.io/api-reference/websockets/auth Upon opening a connection to the server, the connecting client should immediately send a message to the `auth` channel with the user's login information in the form of the auhorization token. After doing this, the connection is "bound" to this user and will receive all information relevant for this user (and that the client is subscribed to). # Notification Source: https://docs.ctechnology.io/api-reference/websockets/notification Receive messages that describe notifications passed to the user. They can have different priorities (e.g., to trigger popups with different colors or of different "invasiveness"). # Vehicle Source: https://docs.ctechnology.io/api-reference/websockets/vehicle Receive messages that describe a vehicle's profile and that are usually sent when something in the vehicle profile changes (e.g., a user updates the profile or there was an automatic reconfiguration triggered by another event). # Vehicle action Source: https://docs.ctechnology.io/api-reference/websockets/vehicleaction Receive messages that describe actions that happen with a given vehicle. In contrast to notifications (that are generated when a user specifically requests it), actions are sent via this channel independently if a user wants to be notified or not. # Vehicle status Source: https://docs.ctechnology.io/api-reference/websockets/vehiclestatus Receive messages that describe updates in the vehicle's status. This message is usually generated when a) the device (installed on a vehicle) communicates with the c.technology system or b) when the c.technology system creates a prediction and thus updates the vehicle status. # AsyncAPI Introduction Source: https://docs.ctechnology.io/asyncapi-reference/introduction Introduction to the c.technology real-time (RT) async API ## Welcome to the c.technology AsyncAPI The c.technology vehicle real-time (RT) async API provides the ability to programmatically interact with real-time components of the c.technology system. This includes real-time events such as alerts, notifications, vehicle status updates, configuration changes, and more. > [!NOTE] > > Please reach out to us for access to OEM-specific fields and endpoints. This > documentation focuses on the general-purpose API used by self-service and > standard customers. ## Key Features * **Real-time Events**: Receive instant updates for vehicle status, notifications, and alerts * **Push-based Updates**: No polling needed - events are pushed as they occur * **WebSocket Connection**: Persistent bidirectional communication * **Webhooks Alternative**: Webhooks are available for selected clients (Beta feature) * **Schema Compatibility**: Message schemas correspond 1:1 to REST API endpoint responses ## How It Works The real-time service uses a plain WebSocket connection. After connecting, authenticate with an application-level message; the server then subscribes the connection based on the user's vehicle permissions. ### Message Structure All messages follow a consistent structure with a header and data section: ```json theme={null} { "header": { "type": "API", "api_version": "v2.2", "channel": "vehicle/status", "uri": "https://api.ctechnology.io/api/v2.2/vehicle/veh_.../status" }, "data": { "vehicle_id": "veh_...", "longitude": 8.5, "latitude": 47.5, ... } } ``` The `uri` field allows you to retrieve the same information via the REST API if needed. ## Authentication To authenticate your connection: 1. Obtain an access token via the [REST API login endpoint](/api-reference/authentication). 2. Send the token to the `auth` channel of the broker. 3. Your connection is now linked to your user account. 4. You'll receive events relevant to your account permissions. ## AsyncAPI vs REST API Choose the right API for your use case: | Feature | AsyncAPI | REST API | | - | - | - | | **Communication** | Push-based | Request / response | | **Updates** | Real-time, instant | On-demand polling | | **Connection** | Persistent WebSocket | Individual HTTP requests | | **Best for** | Live monitoring, dashboards | Data queries, updates | | **Rate limits** | No limits | Rate-limited | # API changelog Source: https://docs.ctechnology.io/changelog/api API changes, new features, and breaking changes in the c.technology platform. ## Backwards compatibility In accordance with [semantic versioning](https://semver.org), major version changes may introduce breaking changes, minor releases add new features in a backward-compatible manner, and patch releases include backward-compatible bug fixes and usability improvements (as such, API requests only use `vX.Y` without the patch version). Please review the breaking changes section for any updates that may require adjustments in your integration. Old releases are supported for **6 months** after a new major or minor version is released. After this period, we recommend updating to the latest version to ensure continued support and access to new features. **v2.2** ### New features * Vehicle command sending * User, security, payment management endpoints * Support tickets, error reporting endpoints **v2.1** ### Major features * API key based authentication * News articles and push notifications **v2.0** ### Major features * Switched all IDs to TypeID format * Streamlined single and paginated formats **v1.2** ### Major features * Vehicle services * Real-time data via WebSockets * Extended vehicle data * Maintenance, alerts, and notifications **v1.0** ### Major features * Initial version of REST API for web and mobile apps * Username / password authentication * Vehicle data retrieval (status, trips, etc.) # App changelog Source: https://docs.ctechnology.io/changelog/app Mobile app updates, new features, and improvements for clickahoy and clickrider apps ## Support of older versions Old app versions are supported for **6 months** after a new major or minor version is released. After this period, we recommend updating to the latest version to ensure continued support and access to new features. **v5.4.0** ### New Features * Setting of home locations in app * Creation of calendar messages in app * Map layer selection **v5.3.0** ### Major Features * Additional protocol support * Additional vehicle functionality: unlocking, sharing, etc. **v5.2.0** ### Major Features * Improved configurability (units, time display, etc.) **v5.1.0** ### Major Features * Vehicle errors and notifications **v5.0.0** ### Major Features * Maintenance scheduling and reminders * White-label toolkit * Vehicle status details improvements **v4.0.0** ### Major Features * Bluetooth connectivity * Offline mode with data caching * Increased configurability and settings * Switchable cockpit screens **v3.0.0** ### Major Features * Complete UI/UX redesign with bottom tabs * Large settings menu on right-most tab * Dashboard screen with vehicle status and quick actions * Support for motorcycles, e-bikes, etc. * Integration with third-party "vehicle services" **v2.0.0** ### Major Features * Notes and documents * Trips and logbook **v1.0.0** ### Major Features * Initial release of the app * Boat tracking and monitoring * Side menu navigation # Platform changelog Source: https://docs.ctechnology.io/changelog/platform Platform / webapp updates, infrastructure improvements, and system-wide changes. ## Support of older versions Platform updates are immediate for all users, and as such older versions are not accessible upon release of a new version. In exceptional cases, individual features may still be accessed using legacy URLs or endpoints. Such versions are supported for **6 months** after a new major or minor version is released. After this period, we recommend updating to the latest version to ensure continued support and access to new features. **Q3 2025** ### Infrastructure & systems * **Trip post-processing**: Trip post-processing with additional data enrichment and analytics. * **Rework of ID system**: Migration of all remaining IDs to UUIDs for improved security and scalability. ### Features & application improvements * **Form hints in webapp**: Contextual hints and help texts in forms throughout the web application. **Q2 2025** ### Infrastructure & systems * **Single sign-on (SSO)**: Support for SAML- and OAuth-based SSO for enterprise customers. * **Status page**: Public status page for real-time system status and incident reporting. * **Unified error handling**: Standardized vehicle error handling and integration with support. ### Features & application improvements * **Improved vehicle dashboard**: Add filtering, error and notifications, and improved status display to professional fleet management dashboard. * **Improved multi-language support**: Added translation support for documents, checklists, etc. **Q1 2025** ### Infrastructure & systems * **Vehicle status permissions**: Granular permissions for accessing vehicle status information. * **Improved scalability of ingress**: Enhanced configurability and auto-scaling for data ingress services. ### Features & application improvements * **Fleet management**: Enhanced tools for fleet tracking, maintenance scheduling, and driver performance analysis for professionals. * **White-labeling and UX/UI improvements**: Custom branding options and improved user interface for a more personalized experience. * **Support for multi-motor boats**: Enhanced NMEA2000 support for boats with multiple engines. **Q4 2024** ### Infrastructure & systems * **Flex CAN support**: Added support for Flex CAN protocol for broader vehicle compatibility. * **Improved TCP receivers**: Enhanced reliability and performance of TCP data receivers. ### Features & application improvements * **Public release of OEM dashboard**: Launch of the original equipment manufacturer (OEM) dashboard for enhanced fleet management and analytics. * **Public release of reworked professional dashboard**: Launch of the redesigned professional dashboard with improved usability and features. * **Webapp themeing**: Customizable themes for the web application to match user preferences or corporate branding. * **Demo of vehicle chatbot**: Introduction of a chatbot feature for vehicle interaction and support. **Q3 2024** ### Infrastructure & systems * **Plug-and-play cable Astra Telematics & NMEA2000**: Simplified installation with plug-and-play cables for Astra Telematics devices and NMEA2000 integration. * **OEM & professional maintenance scheduling**: Advanced maintenance scheduling features for OEMs and professional users. ### Features & application improvements * **Organization user management**: Enhanced user management features for organizations, including role-based access control and improved user provisioning. **Q2 2024** ### Infrastructure & systems * **Improved vehicle services & store**: New backend services for vehicle data processing and a revamped vehicle store for easier management and integration. * **Invoice and billing system automations**: Automated invoicing and billing processes for subscriptions and services. ### Features & application improvements * **Professional and private dashboards rework**: Improved user interface and experience for both professional and private user dashboards. * **Subscription barriers for privates**: Introduction of subscription models for private users to access premium features. **Q1 2024** ### Infrastructure & systems * **NMEA2000 support for Astra Telematics**: Added support for NMEA2000 protocol in Astra Telematics devices for enhanced marine data integration. * **Support ticket system**: Implementation of a support ticketing system for better customer service and issue tracking. * **Invoice and billing system**: New invoicing and billing system for managing subscriptions and payments. ### Features & application improvements * **Webapp white-labeling**: Custom branding options for businesses using the platform. * **IoT device management console**: Centralized management interface for connected IoT devices. * **Vehicle, user, and IoT device management**: Enhanced management features for vehicles, users, and IoT devices. # Roadmap Source: https://docs.ctechnology.io/changelog/roadmap An outlook on upcoming features and improvements for c.technology platform and apps. > [!NOTE] > > Please note that the roadmap is subject to change and timelines are > approximate. **2026** ### Platform improvements * Self-registration and onboarding for new organizations * Quick configuration of vehicle status data / fields * Enhanced data privacy controls and compliance features * Webhooks for real-time data updates and integrations * OEM-configurable payment and subscription infrastructure * Continuous improvements of OEM management dashboard and developer access ### App enhancements * Bluetooth background connectivity improvements * Enhanced offline mode with more robust data caching and sync * Additional specialized map layers and navigation features ### API changes * Deprecation of legacy endpoints (support errors, etc.) * Webhook configurations and management endpoints * Subscription and payment management endpoints # Data upload Source: https://docs.ctechnology.io/developer/getting-started/data-upload Complete guide to uploading vehicle data and managing vehicle commands in the c.technology platform. The c.technology platform processes real-time vehicle data ingested via different endpoints, and allows relaying commands back to a vehicle via similar channels. This guide covers both uploading data from vehicles and sending commands back to vehicles. Generally, you will have to differentiate between: * **Data from an IoT device**: In this case, a custom TCP endpoint or an MQTT broker is commonly used. This guide does *not* cover this scenario. Please refer to the [hardware section](/hardware/introduction) for more information about devices supported out of the box. * **Data ingested via HTTP endpoints**: This scenario covers mobile app relay connections, cloud-to-cloud solutions, and "heavier" IoT devices that can communicate via HTTPS. This guide focuses on this scenario. Via the c.technology platform, you can not only upload data via the mentioned HTTP endpoints, but also manage your IoT devices. This is usually in collaboration with the IoT device manufacturer's management portal: ![](https://mintcdn.com/ctechnologyag/zNY5n_oF4ow67xSx/images/developer/iot-connectivity-management.png?fit=max\&auto=format\&n=zNY5n_oF4ow67xSx\&q=85\&s=923e1feb244ef5e55eb2654d6e7297bf) ## Retrieve upload token The ingestion endpoints are separated from the main REST API for security and scalability reasons. As such, you first need to obtain an upload token for your vehicle before you can upload data. To do this, you either need upload access directly as a vehicle owner, or federated upload access via an organization. As a vehicle owner (this is primarily important if you use an app as a data relay, as only the user is logged in there, and you should not expose your API key into an app), use the following request: ```bash theme={null} curl https://api.ctechnology.io/api/v2.2/security/vehicle/{vehicle_id}/vehicle-data-upload-token \ -H "Authorization: Token YOUR_USER_TOKEN" ``` On the other hand, if you're in a secure backend (or embedded) environment and can use your organization's API key, use the following request: ```bash theme={null} curl https://api.ctechnology.io/api/v2.2/security/vehicle/{vehicle_id}/vehicle-data-upload-token \ -H "Authorization: Api-key YOUR_VEHICLE_UPLOAD_API_KEY" ``` > [!NOTE] > > The `YOUR_VEHICLE_UPLOAD_API_KEY` must be an API key that has the > `VEHICLE_DATA_UPLOAD` permission for the indicated vehicle. You can create > such an API key as described [here](#retrieve-vehicle-upload-api-key). Finally, if you want a global upload token for all vehicles in your organization, you can use the following request. > [!WARNING] > > This should *only* be used for cloud-to-cloud integrations where you can > securely store the token, as it allows uploading data for *all* vehicles in > your organization. ```bash theme={null} curl https://api.ctechnology.io/api/v2.2/security/organization/{organization_id}/vehicle-data-upload-token \ -H "Authorization: Api-key YOUR_ORG_API_KEY" ``` Any of these requests will return a JWT (including either the vehicle or organization id, the expiration date, and some internally used information) that you can use to authenticate your data upload requests: ```json theme={null} { "header": { ... }, "data": { "token": "your-upload-token", } } ``` ### Retrieve vehicle upload API key To create an API key with the `VEHICLE_DATA_UPLOAD` permission for a specific vehicle, use the following request: ```bash theme={null} curl -X POST https://api.ctechnology.io/api/v2.2/security/api-key \ -H "Authorization: Api-key YOUR_ORG_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "role": "VEHICLE_UPLOAD_DATA", "vehicle_id": "veh_12345", "name": "upload-api-key" }' ``` ## Authenticate with ingress and obtain session token The ingress service itself uses short-lived session tokens to authenticate vehicles. These session tokens are tied to a specific vehicle and include metadata such as the vehicle UUID. > [!NOTE] > > You will have to refresh the session token periodically or when it expires. Request a session token by making the following request: ```bash theme={null} curl -X POST https://ingress.ctechnology.io/auth/ \ -H "Content-Type: application/json" \ -d '{ "token": "your-upload-token" }' ``` The response will contain a session token that you can use for subsequent data uploads: ```json theme={null} { "session_token": "your-session-token", "expiration_date": "2025-10-10T10:39:06.514Z" } ``` ## Upload vehicle data To upload vehicle data, use the session token obtained in the previous step to authenticate your requests. Make the following request to upload data: ```bash theme={null} curl -X POST https://ingress.ctechnology.io/update/base/ \ -H "Content-Type: application/json" \ -d '{ "update": { "timestamp": "2025-10-10T10:41:19.556Z", "longitude": 8.5417, "latitude": 47.3769 }, "session_token": { "token": "your-session-token" } }' ``` See the [ingress documentation](https://ingress.ctechnology.io/docs) for the supported endpoints, data formats, and other ways to pass the session token. If you have a custom data upload endpoint, you will receive it directly from c.technology. ## Vehicle Command System The platform enables bidirectional communication with vehicles through a sophisticated command queuing system that ensures reliable delivery and execution of commands. Commands are sent through the vehicle command API with low or high priority delivery. Make the following request to enqueue a command: ```bash theme={null} curl -X POST https://api.ctechnology.io/api/v2.2/vehicle/{vehicle_id}/command/ \ -H "Authorization: Token YOUR_TOKEN" \ -H "Content-Type: application/json" \ -d '{ "command": "LOCK", // see REST API docs for supported commands "priority": "HIGH", // or "LOW" "timestamp_planned_execution": null, // or ISO 8601 timestamp for scheduled execution }' ``` ### Command Priority Levels The system supports two priority levels with different delivery mechanisms: #### `HIGH` priority commands * Delivered with the platform's active delivery mechanism when the vehicle connects (SMS, push via GPRS, etc.). * Intended for commands that should be delivered before regular queued data. #### `LOW` priority commands * Queued and delivered when the vehicle next connects. * Suitable for routine or scheduled changes. ### Command Status and Tracking > [!WARNING] > > This is currently under development and may not be supported in all > environments. You can track command delivery and execution status: ```bash theme={null} curl -X GET https://api.ctechnology.io/api/v2.2/vehicle/{vehicle_id}/command/ \ -H "Authorization: Token YOUR_TOKEN" ``` ## Data Upload Best Practices Please consider the following best practices when uploading data. ### Optimal Upload Frequency Balance data freshness with bandwidth and battery consumption: * **Moving mode**: Every 5-10 seconds for active vehicles * **Stationary mode**: Every 10-30 minutes for parked vehicles * **Power-saving mode**: Every 30 minutes to 3 hours for low battery scenarios * **Event-Triggered**: Immediate upload for critical events ### Batch Upload Strategy > [!WARNING] > > Batch uploads are currently under development and may not be supported in all > environments. ### Security Considerations Ensuring tokens are secure is crucial to keep clean and reliable data, and prevent tampering: * **Token Management**: You *must* securely store API keys and periodically refresh session tokens. * **Data Encryption**: All endpoints require the use of HTTPS for all data transmission. * **Rate Limiting**: APIs are rate-limited. You will be informed via HTTP 429 responses if you exceed limits. Implement exponential backoff and retry logic. ## Troubleshooting This section may help you resolve common issues during data upload and command management. > **Authentication problems** > > Verify that the upload token and session token are correct and have not > expired. Ensure the vehicle is registered and associated with the correct > organization or user. > **Data upload failures** > > Check the data format against the expected schema. Ensure all required fields > are present, especially the timestamp. Validate numeric ranges for sensor > values. > **Command delivery failures** > > Ensure the vehicle is online and has a stable connection. Check command > priority and adjust if necessary. > **Rate limiting errors** > > Implement exponential backoff retry logic. Reduce upload frequency if hitting > rate limits. Consider batch uploading multiple data points. # Organization setup Source: https://docs.ctechnology.io/developer/getting-started/setup-organization Complete guide to setting up your organization in the c.technology platform. Users, vehicles, and **organizations** are the foundation of the c.technology platform, providing the multi-tenant structure that enables different types of entities to manage their vehicles, users, and data independently. This guide covers the complete process of organization creation, configuration, and ongoing management. > [!NOTE] > > If you are interested in using the web application for organization management, please refer to the [c.technology web app documentation](/handbook/oem/introduction). Organizations represent different types of entities, usually everything that has a legal business representation and / or consists of multiple users and vehicles: * **OEMs**: Vehicle manufacturers who produce and sell vehicles equipped with c.technology systems. * **Professional partners**: Dealers, service providers, and fleet operators who serve vehicle owners. Users can either "just" be individual vehicle owners or belong to an organization that manages multiple vehicles and users. Being part of an organization enables individual users to access the organization's vehicles based on the transitive permissions thus given. While users can be part of organizations, they often also just interact with those (e.g., vehicle owners interacting with a dealer organization), as visualized below: ![](https://mintcdn.com/ctechnologyag/zNY5n_oF4ow67xSx/images/developer/vehicle-access.png?fit=max\&auto=format\&n=zNY5n_oF4ow67xSx\&q=85\&s=10ac236c77d28744a0b79e70d48f199e) Similarly, vehicles can either be owned by individual users or belong to one or more organizations that manage them. ## Organization creation Currently, you *must* contact [support@ctechnology.io](mailto:support@ctechnology.io) to create a new organization. > [!NOTE] > > In the future, self-service organization creation will be available. We will set up an organization for you and add you as an administrator. Note that organization creation requires a business relationship in every case, as it involves billing, security, and access control setup. You can find the different subscription types and pricing on [ctechnology.io](https://ctechnology.io). When contacting c.technology, please specify your organization type to ensure proper configuration: * **OEM**: If you are a vehicle manufacturer producing vehicles with c.technology systems. * **Professional**: If you are a dealer, service provider, or fleet operator serving vehicle owners. Upon organization creation, you should create an API key for programmatic access to the platform. You can do this in the `DEVELOPER` section of the [c.technology web app](https://app.ctechnology.io) after logging in. The API key is required for many of the processes described in this documentation, though for several endpoints, you can also use user authentication tokens. # Vehicle access Source: https://docs.ctechnology.io/developer/getting-started/vehicle-access Complete guide to accessing vehicles and managing user permissions in the c.technology platform. Vehicle access in the c.technology platform is controlled through a permission system that enables secure, role-based access to vehicle data and functionality. This guide covers both organizational vehicle access and individual user access scenarios. ## Access control overview Generally, vehicle access is managed by two "barriers": * **Permission barrier**: There are permissions for individual vehicles, as well as individual datapoints recorded by a vehicle. Permissions can be granted directly to users, or inherited via organizational membership. * **Subscription barrier**: Similarly, there are subscription levels that determine which features and data types are available for a vehicle. Subscription levels can be assigned to individual vehicles, or inherited via organizational membership. ![](https://mintcdn.com/ctechnologyag/zNY5n_oF4ow67xSx/images/developer/authentication-access.png?fit=max\&auto=format\&n=zNY5n_oF4ow67xSx\&q=85\&s=2736bbd6c841ef0fb2e407af7aa85087) Note that federated vehicle access (via an organization) is handled fully transparently by the platform. As such, users do not need to be aware of whether they are accessing a vehicle directly or via an organization. However, for every request you can see the "reason" why you were able to perform it by inspecting the `permission_via` field in the `header` of the response. This will show either `via: me` or `via: organization`, including additional information about the permission source, and organization. If you have multiple permissions for a vehicle, all applicable sources will be listed. ## Understanding vehicle permissions The permission system uses an exhaustive list of individual permissions that can be granted to users and organizations for vehicles. Important example permissions include: * **VEHICLE\_STATUS\_VIEW**: Full access to vehicle location, sensor data, and operational status * **VEHICLE\_LOGBOOK\_VIEW**: Access to trip history and event logs * **VEHICLE\_STATUS\_ANONYMIZED**: Access to vehicle data without location information * **VEHICLE\_PROFILE\_EDIT**: Ability to modify vehicle settings and configuration * **VEHICLE\_CAN\_UNLOCK**: Permission to unlock vehicle doors remotely ## Permissions for individual users Each user can have permissions for the user account itself, as well as for an arbitrary number of individual vehicles. \[!WARNING] Any change to individual user permissions will be immutably logged in the audit log, including information about who made the change and when. ## Permissions in the context of organizations Organizations can have permissions for each member, as well as for the organization's vehicles. Members (usually, though this may be restricted based on their permissions within the organization) inherit permissions for all vehicles owned by the organization, as well as vehicles shared with the organization. # Vehicle registration Source: https://docs.ctechnology.io/developer/getting-started/vehicle-registration Step-by-step guide to registering vehicles in the c.technology platform. Vehicle registration is the process of creating a new digital twin for a vehicle on the c.technology platform. The digital twin can then be fed data via the different endpoints, as described in the [data upload section](/developer/getting-started/data-upload). ## Prerequisites Before registering a vehicle, ensure you have: * Valid c.technology API credentials with appropriate permissions * Vehicle identification information (VIN, registration, etc.) * IoT device details *if* you are using an IoT device (IMEI, ICCID, etc.) * Set up your organization's vehicle taxonomy and parts, if applicable > [!WARNING] > > If you have purchased IoT devices and SIM cards from c.technology, they are pre-configured to work with the platform. You will only need your device ID to associate the vehicle with your organization. ## Registration Using the API, you can register vehicles programmatically. \[!NOTE] For single vehicle registrations, it may be more convenient to use the [c.technology web application](https://app.ctechnology.io). Execute the following API call to register a new vehicle: ```bash theme={null} curl -X POST https://api.ctechnology.io/api/v2.2/organization/{organization_id}/vehicle/ \ -H "Authorization: Api-key YOUR_ORG_API_KEY" \ -H "Content-Type: application/json" \ -d '{ "name": "My vehicle name", "organization_vehicle_id": "FLEET001", "organization_vehicle_type_id": "vtpe_1234", "organization_vehicle_name": "Fleet Vehicle 001", "organization_location_main_desc": "North Depot", "vehicle_identification_number": "ABC123", "vehicle_registration_id": "XYZ789", "drivetrain_type": "ELECTRIC", "hardware_type": "BLUETOOTH", "vehicle_type": "CAR", "iot_name": "device_001", "vehicle_parts": [ { "organization_part_id": "part_123", "instance_id": "instance_001" } ] }' ``` ### Required and optional fields The only **required** field is `name`, which is the display name for the vehicle in the c.technology platform. However, depending on your organization type, additional fields may be effectively required or behave differently: #### OEM organizations If your organization is an **OEM** (vehicle manufacturer), you **must** provide `organization_vehicle_type_id`, which references a vehicle type defined in your organization's taxonomy. OEMs can also specify a custom `organization_vehicle_id` (your internal identifier for the vehicle), which will be uppercased and used as the vehicle's unique identifier in the system. If not provided or left empty, a random 8-character ID will be generated. > [!WARNING] > > For OEMs, the `organization_vehicle_id` has a maximum length limit. Ensure your custom IDs don't exceed this limit to avoid validation errors. OEMs are automatically assigned the `VEHICLE_MANUFACTURER` role for vehicles they register, regardless of any `role` field provided. #### Professional and other organizations For **professional organizations** (dealers, service providers, fleet operators) and other organization types: * `organization_vehicle_id` is optional and will be automatically generated as a random 8-character ID if not provided. * `organization_vehicle_type_id` is optional (not required unlike for OEMs). * You can specify the organization's relationship to the vehicle using the `role` field with values `VEHICLE_MAINTAINER` or `VEHICLE_OWNER`. ### Input methods The API supports two methods for providing organization-specific vehicle data: **Method 1: Direct properties** (recommended for single organization scenarios) ```json theme={null} { "name": "My vehicle", "organization_vehicle_type_id": "vtpe_1234", "organization_vehicle_id": "FLEET001", "organization_vehicle_name": "Fleet Vehicle 001", "organization_location_main_desc": "North Depot", "role": "VEHICLE_OWNER" } ``` **Method 2: Nested `organization_vehicles` array** (useful for multi-organization scenarios) ```json theme={null} { "name": "My vehicle", "organization_vehicles": [ { "organization_id": "{organization_id}", "vehicle_type_id": "vtpe_1234", "organization_vehicle_id": "FLEET001", "organization_vehicle_name": "Fleet Vehicle 001", "location_main_desc": "North Depot", "role": "VEHICLE_OWNER" } ] } ``` > [!NOTE] > > When using the nested method, the `organization_id` in the nested object must match the one in the URL path. Values in the nested object will override any direct properties. ### Additional parameters Beyond the core identification fields, you can provide: * **`vehicle_identification_number`**: The vehicle's VIN (Vehicle Identification Number) * **`vehicle_registration_id`**: The vehicle's license plate or registration number * **`drivetrain_type`**: The vehicle's drivetrain type (e.g., `GASOLINE`, `ELECTRIC`, `DIESEL`, `HYBRID`) * **`hardware_type`**: The IoT hardware type installed (e.g., `BLUETOOTH`, `NONE`) * **`vehicle_type`**: The general vehicle classification (defaults to your organization's primary vehicle type if not specified) * **`iot_name`**: The IoT device identifier * **`vehicle_parts`**: An array of vehicle parts to associate with the vehicle ### Vehicle parts If your organization has defined a parts taxonomy, you can assign parts to vehicles during registration: ```json theme={null} { "vehicle_parts": [ { "organization_part_id": "part_123", "instance_id": "instance_001" } ] } ``` > [!NOTE] > > The field `organization_vehicle_part_id` is also supported for backwards compatibility, but `organization_part_id` is the recommended field name. Each part requires: * `organization_part_id`: The ID of the part type as defined in your organization's parts taxonomy * `instance_id` (optional): A unique identifier for this specific instance of the part Please refer to the [API reference](/api-reference/introduction) for the complete list of parameters and their descriptions. ### Response Upon successful registration, you will receive a HTTP 200 response with the complete vehicle profile: ```json theme={null} { "header": { "api_version": "v2.2", "status": "success" }, "data": { "id": "veh_12345", "seaborne_id": "FLEET001", "name": "My vehicle name", "organization_id": "org_123", ... } } ``` The response includes the vehicle's unique identifier (`id`), the internal identifier (`seaborne_id`), and all other vehicle properties. > [!NOTE] > > After successful registration, permission caches are automatically refreshed to ensure the vehicle appears immediately in your queries. ### Updating vehicles If you need to change the vehicle type or other details later, you can use the `PUT /organization/{organization_id}/vehicle/{vehicle_id}` endpoint. Similarly, you can manage vehicle part assignments using the `/vehicle/{vehicle_id}/vehicle-part/` endpoints after registration. ## Bulk registration For bulk registrations, you may upload CSV files via the [c.technology web app](https://app.ctechnology.io) or use the API to register multiple vehicles in a loop. ## Troubleshooting This section may help you resolve common issues during vehicle registration. > **SIM card configuration errors** > > If you encounter SIM card configuration issues, log into your carrier's portal (e.g., 1nce, 1ot, emnify, etc.) and verify the SIM card ICCID is correct and the SIM is active. > **Device communication issues** > > If you experience problems with device connectivity, ensure the device is powered on and has a stable cellular connection. > Often, devices may take several minutes to register on the network after initial power-up. > Similarly, GPS modules may take time to acquire a satellite fix, and upon initial startup may not send data before a fix is acquired (due to aquiring a correct timestamp via GPS). > **API validation failures** > > Common validation errors and their solutions: > > **Organization-related errors:** > > * **Organization does not exist**: Verify the `organization_id` in the URL is correct and the organization exists. > * **Missing `organization_vehicle_type_id` for OEMs**: OEM organizations must provide a valid vehicle type ID. Verify the vehicle type exists in your organization's taxonomy. > * **Vehicle type does not exist**: The provided `organization_vehicle_type_id` doesn't match any vehicle type in your organization. Check your organization's vehicle type definitions. > > **Field validation errors:** > > * **Invalid drivetrain type**: Ensure the `drivetrain_type` is one of the supported values (e.g., `GASOLINE`, `ELECTRIC`, `DIESEL`, `HYBRID`). > * **Invalid hardware type**: Verify the `hardware_type` is a valid option (e.g., `BLUETOOTH`, `NONE`). > * **organization\_vehicle\_id too long**: For OEMs, custom vehicle IDs have a maximum length. Use shorter identifiers or let the system generate one. > > **Vehicle parts errors:** > > * **Vehicle part does not exist**: The specified `organization_part_id` doesn't exist in your organization's parts taxonomy. Verify the part ID is correct. > > **Transaction failures:** > > * If vehicle creation fails mid-process, all changes are automatically rolled back to maintain data consistency. Check the error message for specific details about what failed. > > **Permissions:** > > * **Missing permissions**: Your API key or user token lacks vehicle creation permissions for the specified organization. # Developer introduction Source: https://docs.ctechnology.io/developer/index Getting started with c.technology systems, APIs and development resources. ![c.technology logo](https://mintcdn.com/ctechnologyag/NPQ2ln3oN-_JqwFH/logo/ctechnology-light.png?fit=max\&auto=format\&n=NPQ2ln3oN-_JqwFH\&q=85\&s=a2b2602fb0b3413f4f112b8cbbf5377a) Modern vehicles generate enormous amounts of data - from GPS coordinates and engine diagnostics to environmental sensors and user interactions. The c.technology developer platform abstracts the complexity of vehicle connectivity, data processing, and real-time synchronization, allowing you to focus on creating exceptional user experiences rather than managing infrastructure. From simple location tracking to sophisticated predictive maintenance algorithms, the platform scales with your needs while maintaining enterprise-grade security and reliability. The platform is essentially sliced into three layers: * **Applications**: Web and mobile apps, dashboards, reporting tools, and developer SDKs. * **Systems**: Storage services, data processing pipelines, API gateways, authentication services, payment processing, and analytics engines. * **Infrastructure**: Scalable containerized cloud services, real-time and spatial databases, message queues, and IoT connectors. ![](https://mintcdn.com/ctechnologyag/zNY5n_oF4ow67xSx/images/developer/3-tech-layers.png?fit=max\&auto=format\&n=zNY5n_oF4ow67xSx\&q=85\&s=4f0e280a1d2564520632532ad0d5242c) Usually, as a developer, you will interact with the systems layer via APIs, while using the applications layer to manage your account, vehicles, and data. Commonly, you do not have to concern yourself with the underlying infrastructure, as it is fully managed by us. ## System architecture The following diagram provides a high-level overview of the c.technology platform architecture, illustrating how different components interact to deliver a seamless vehicle connectivity experience. ![](https://mintcdn.com/ctechnologyag/zNY5n_oF4ow67xSx/images/developer/system-overview.png?fit=max\&auto=format\&n=zNY5n_oF4ow67xSx\&q=85\&s=96a04f0bc2c1e8b9bfe3c6b2427b499f) Of most interest to developers are the vehicle data ingestion points (or more generally, communication connectors), and the REST and real-time APIs that provide access to vehicle data and platform functionality. ### Vehicle communication Vehicles connect to the platform through a variety of communication methods: * **Telematics units**: We collaborate with manufacturers whose devices work out of the box with our platform (see the [hardware section](/hardware/introduction) for details). Other devices can be integrated via standard protocols or custom connectors developed with us. * **Mobile apps**: Our SDKs enable mobile applications to act as intermediaries, relaying data between vehicles and the platform. * **Cloud-to-cloud integrations, other custom setups**: Via HTTP APIs or MQTT brokers, vehicles living on existing cloud platforms can be integrated with our system. The quickest options are telematics units that support standard protocols such as OBD2 or NMEA 2000, devices with a known CAN-bus specification (DBC file), or the HTTP ingestion endpoints. ### REST APIs for core functionality Our primary API follows REST conventions with a complete OpenAPI specification that enables automatic code generation and interactive documentation. Authentication uses tokens. Users obtain tokens with email and password; organizations (usually) use API keys, which are sent in the same header as `Authorization: Api-key ...`. Rate limiting ensures fair usage across all clients while preventing abuse. Generally, you will use the web interface for initial setup and configuration, as well as team and billing management, and occasional vehicle and support tasks. You then may use the REST API for other platform operations, including: * **Vehicle management**: Register vehicles, update configurations, and manage vehicle groups. * **Data retrieval**: Access historical vehicle data, trip logs, and sensor readings. * **Command and control**: Send commands to vehicles, such as locking/unlocking doors or starting/stopping engines. ### Real-Time APIs For applications requiring immediate updates, the WebSocket-based real-time API delivers vehicle data as events occur. This supports updates to the following data types: * **Vehicle status updates**: Location changes, speed, fuel levels, and other telemetry data. * **Vehicle profile updates**: Changes to vehicle configurations or user preferences. * **Alerts and notifications**: Immediate alerts for critical events like accidents, theft attempts, or maintenance issues. The real-time API is specified as an AsyncAPI document that details all available real-time events and their data structures. ### SDKs for building applications From the OpenAPI and AsyncAPI specifications, a number of generators can be used to create client libraries in various programming languages. Officially, we support a TypeScript SDK to provide a seamless integration experience for web and mobile applications. ## Getting Started The quickest path to integration starts with authentication and basic API exploration. Once you have valid credentials, the platform opens up its full capabilities for vehicle management, real-time monitoring, and data analysis. > [!NOTE] > > Another quick way to get started is by purchasing a pre-configured telematics > device from our marketplace that automatically connects to the platform. Like > this, you can start using all systems with zero setup. ### 1. Authentication Setup Set up your account by heading to the [c.technology web app](https://app.ctechnology.io) and registering as a new user. Reach out to [support@ctechnology.io](mailto:support@ctechnology.io) to upgrade your account to an organizational account with developer access. > [!NOTE] > > In the future, self-service account upgrades will be available. Use the authentication API to obtain an access token for subsequent API requests: ```bash theme={null} # Get your access token curl -X POST https://api.ctechnology.io/api/v2.2/account/login/ \ -H "Content-Type: application/json" \ -d '{"email": "your-email", "password": "your-password"}' ``` You will receive a response containing your access token: ```json theme={null} { "header": { ... }, "data": { "token": "YOUR_TOKEN", "expiry": "2024-12-31T23:59:59Z", "user": { ... } } } ``` ### 2. API Exploration As a first example, retrieve your user profile using the access token obtained in the previous step: ```bash theme={null} # Test API access curl -H "Authorization: Token YOUR_TOKEN" \ https://api.ctechnology.io/api/v2.2/me ``` If you received a response containing `"data": { "id": ..., "email": "your-email", ... }`, your authentication was successful, and you can proceed to explore other API endpoints. ### 3. OpenAPI and SDK installation Head over to the [REST API documentation](/api-reference/introduction) to explore all available endpoints and their capabilities. Download the OpenAPI specification to generate client code, e.g., using `openapi-generator-cli`: ```bash theme={null} # Generate the TypeScript SDK npx @openapitools/openapi-generator-cli generate --generator-key typescript-fetch \ -i ctechnology-openapi.json \ -o ./api-gen/ctechnology-sdk ``` ### 4. Basic Integration Integrate the generated SDK into your application to start interacting with the platform programmatically: ```typescript theme={null} import { Configuration, UsersApi } from "./api-gen/ctechnology-sdk"; const config = new Configuration({ basePath: "https://api.ctechnology.io/api/v2.2", apiKey: "Token your-api-key", }); const usersApi = new UsersApi(config); const user = await usersApi.meGet(); console.log(user); ``` ## Development resources The most important resource is the documentation you are currently reading. If you find any gaps or have suggestions for improvement, please reach out to [support@ctechnology.io](mailto:support@ctechnology.io). Similarly, if you want to get started with a trial immediately, or need help with integration, setup, customization, please check our offers on [ctechnology.io](https://ctechnology.io) or contact us directly. ## Next Steps * [Organization setup](/developer/getting-started/setup-organization) - Continue with the getting started guide by learning about users and organizations * [Platform Basics](/developer/platform-basics) - Core concepts and architecture * [Integration Examples](/developer/integration-examples) - Real-world implementation examples * [API Reference](/api-reference/introduction) - Complete API documentation # IDs Source: https://docs.ctechnology.io/developer/platform-basics/ids General structure and usage of unique identifiers in the c.technology platform. Generally, all entities in the c.technology platform are identified by a unique identifier (ID) in [TypeID format](https://github.com/jetify-com/typeid). TypeIDs are UUIDs with a prefix that indicates the type of entity, making it easy to identify and manage different types of objects within the platform: ```json theme={null} { // Example vehicle ID in TypeID format. "id": "veh_01jnk61e5pf6zs5ag6483xqe43" } ``` The only exception to this are organization IDs, which use reverse domain names (e.g. `com.demoCompany`) instead of TypeIDs. See the [Organizations](organization) documentation for details. For users, email addresses can be used as an alternative unique identifier, as they are guaranteed to be unique within the platform. # Notifications Source: https://docs.ctechnology.io/developer/platform-basics/notification How notifications are structured and used within the c.technology platform. Notifications are messages or alerts sent to users or systems to inform them about specific events or updates related to vehicles, trips, or other activities within the c.technology platform. ## Notification structure Notifications are structured as follows: ```json theme={null} { "id": "notif_01k5pq8tznf78s77cnhj0bz0ma", "type": "USER_BAT_V", // Type of notification, e.g., USER_BAT_V (user battery voltage). "timestamp": "2025-09-21T18:06:08+0000", // Time the notification was created. "priority": "HIGH", // Priority of the notification: LOW, MEDIUM, HIGH. "vehicle_id": "veh_01jnk61et0fxkbvb3t05w9gv0d", // The vehicle the notification is associated with. "title": "Notification from c.technology", // Human-readable title of the notification. "message": "Demo Electric Motorcycle : low battery.", "data": { // Additional data associated with the notification. "battery_voltage": 10.035 }, "read": false // Indicates if the notification has been read by the user. } ``` # Organizations Source: https://docs.ctechnology.io/developer/platform-basics/organization Understanding organizational structure and multi-tenancy in the c.technology platform. Organizations represent any entity that manages vehicles, users, and data within the c.technology platform. This includes vehicle manufacturers (OEMs), dealerships, fleet operators, and service providers, among others. ## Organization structure Organizations are structured as given below. > [!NOTE] > > Organizations are the *only* entity within the c.technology platform that do not use UUIDs / TypeIDs as identifiers. Instead, they use reverse domain names (e.g. `com.demoCompany`). ```json theme={null} { "id": "com.demoCompany", // Unique organization ID, as a reverse domain name. "primary_vehicle_type": "BOAT", "organization_type": "OEM", // Type of organization: OEM, PROFESSIONAL. "name": "Demo Company", "email": "oem@demo.com", "support_email": null, "email_new_message": true, "telephone": "0041234567890", "website": "www.ctechnology.io", "addr_street": "Tessinerplatz 07", "addr_city": "Zürich", "addr_zip": "8004", "addr_country": "Switzerland", "longitude": 8.532224063229377, "latitude": 47.36412910278374, "preferred_contact_via": "EMAIL", "general_theme": { // General branding and theming settings for web and mobile apps. "webapp": "https://app.ctechnology.io", "appName": "ctechnology", "website": "https://ctechnology.io", "textColor": "#ffffff", "primaryColor": "#001f3f", "secondaryColor": "#F9413C", "primaryColorTransparent": "rgba(0, 178, 178, 0.2)", "secondaryColorTransparent": "rgb(0, 179, 184, 0.2)" }, "vehicle_theme": null, "auto_invoice": false, "developer_access": true, // Whether the organization has developer access to APIs and API keys. "logo_url": "...", "logo_square_url": "...", "favicon_url": "...", "dashboard_background_url": "...", "managed": true // Whether the organization is managed by another organization or independent. } ``` ## Organization members Organization members are represented as a stripped-down user object with additional role and permission information. ```json theme={null} { "user": { "id": "usr_01jnk61cv5ev1a1ty1136gfwh6", "email": "demo@ctechnology.io", "first_name": "Demo", "last_name": "User", "profile_picture_url": "/static/img/dude.png" }, "role": "USER_ORG_ADMIN", "permissions": [] } ``` ## Organization vehicles When retrieveing vehicles, the format corresponds to the format explained in the [vehicle section](/developer/platform-basics/vehicle). ## Organization partners Partner organizations are organizations that have a professional relationship with your organization. For example, as a vehicle manufacturer, you may have partnerships with dealerships, service providers, or mechanics. As such, they are represented with the same structure as organizations above, potentially with restricted access to individual fields. ## Multi-tenancy on the c.technology platform The c.technology platform is designed as a multi-tenant system where multiple organizations can operate independently while sharing the same underlying infrastructure. For example, you as a vehicle manufacturer may have your own organization, running on the same platform as a fleet operator or dealership, but with separation according to strict access rules. > [!NOTE] > > Please contact [support@ctechnology.io](mailto:support@ctechnology.io) or your customer representative if you have questions or additional requirements regarding multi-tenancy and organizational structure. ## Billing and subscriptions Organization-level billing includes subscription management with plans and features at the organization level, usage-based pricing with charges based on vehicle count, multi-tier pricing with different pricing for different organization types, and volume discounts with reduced pricing for large-scale deployments. Upon creating an organization, you will receive a monthly invoice based on your subscription plan and vehicle count. # Permissions Source: https://docs.ctechnology.io/developer/platform-basics/permission Understanding the role-based permission system for granular access control in the c.technology platform. The c.technology platform implements a sophisticated role-based access control (RBAC) system that provides granular control over what users can see and do within the platform. This permission system operates at multiple levels, from high-level feature access down to individual sensor data fields, ensuring appropriate data visibility while maintaining security and compliance requirements. ## Permission system architecture The permission system is built on three core concepts that work together to provide flexible and scalable access control: 1. **Permissions** - Atomic capabilities that define specific actions or access rights (down to temporally restricted access to individual data fields) 2. **Roles** - Collections of permissions that represent common job functions or access patterns 3. **Assignments** - The binding of roles to users for specific contexts (vehicles, organizations) Additionally, permissions are transitive through organizational hierarchies, meaning that users inherit permissions based on their organization memberships and the roles assigned to those organizations for specific vehicles. This architecture enables fine-grained control while remaining manageable for administrators and intuitive for end users. ## Permission categories The platform organizes permissions into distinct categories that makes permissions easy to understand and manage: ### User permissions General permissions that control a user's access to platform-wide functionality: ```python theme={null} # Example user permissions USER_PROFILE_VIEW # Access to user profile data (read-only) USER_PROFILE_EDIT # Access to user profile data (can edit) USER_ASSIGN_VEHICLE_TO_USER # Allowed to assign vehicles to users USER_NOTIFICATION_ALERT_VIEW # Access to notification alerts (read-only) USER_GEOFENCING_VIEW # Access to user-defined geofencing (read-only) USER_GEOFENCING_EDIT # Access to user-defined geofencing (can edit) ``` These permissions control access to personal settings, notification management, geofencing configuration, and other user-centric features. ### Vehicle permissions Permissions that control access to specific vehicle data and functionality: ```python theme={null} # Example vehicle permissions VEHICLE_STATUS_VIEW # Access to vehicle status (current data) VEHICLE_LOGBOOK_VIEW # Access to logbook VEHICLE_LOGBOOK_DETAIL_VIEW # Access to detailed logbook parameters VEHICLE_LOGBOOK_DETAIL_EDIT # Can edit trip name, comments, captain VEHICLE_PROFILE_EDIT # Can edit vehicle profile information VEHICLE_OWNERS_EDIT # Can modify vehicle ownership ``` Vehicle permissions provide the core access control for vehicle data, from basic status viewing to detailed operational control. ### UI user permissions Permissions that control which user interface elements are visible in web applications: ```python theme={null} # Example UI user permissions UI_USER_NAVBAR_DASHBOARD # Show dashboard in navigation UI_USER_NAVBAR_VEHICLES # Show vehicles section in navigation UI_USER_NAVBAR_PROFILE # Show profile section in navigation UI_USER_NAVBAR_BILLING # Show billing section in navigation ``` These permissions enable customization of the user interface based on user roles and organizational needs. ### UI vehicle permissions Permissions that control vehicle-specific UI elements and data presentation: ```python theme={null} # Example UI vehicle permissions UI_VEHICLE_STATUS_BATTERY # Show battery information in vehicle status UI_VEHICLE_STATUS_FUEL # Show fuel information in vehicle status UI_VEHICLE_LOGBOOK_MAP # Show map view in logbook UI_VEHICLE_MAINTENANCE_TAB # Show maintenance tab ``` ### App permissions Permissions specific to mobile application functionality: ```python theme={null} # Example app permissions UI_APP_VEHICLE_LOCK_UNLOCK # Show lock/unlock controls in mobile app UI_APP_NOTIFICATIONS_PUSH # Enable push notifications UI_APP_OFFLINE_MODE # Allow offline data access ``` ### Organization permissions Permissions that control organizational management and administration: ```python theme={null} # Example organization permissions USER_ORG_GENERAL_ACCESS # Basic organization access USER_ORG_SETTINGS_EDIT # Can edit organization settings USER_ORG_MEMBER_ADD # Can add new organization members USER_ORG_MEMBER_REMOVE # Can remove organization members ``` ## Sensor-Level Permissions Beyond functional permissions, the platform implements granular sensor-level permissions that control access to individual data fields within vehicle status models. This capability is essential for data privacy compliance by restricting access to location or personal data, commercial data protection for proprietary sensor information, role-based data filtering where different users see different data sets, and regulatory compliance for industry-specific data access requirements. ### Sensor Permission Structure Sensor permissions are defined by specifying the exact model and field combination: ```python theme={null} # Example sensor permissions { "key": "vehicle_lat", # Field name in the model "model_name": "VehicleStatus", # Model containing the field "description": "Vehicle GPS latitude coordinate" } # Additional examples { "key": "engine_rpm", "model_name": "VehicleStatusCAN", "description": "Engine RPM from CAN bus" }, { "key": "fuel_level_pct", "model_name": "VehicleStatus", "description": "Fuel level percentage" } ``` ## Predefined Roles The platform includes a comprehensive set of predefined roles that cover common use cases and organizational structures. For user roles, these include: * `USER_STANDARD`: Standard user role. * `USER_READ_ONLY`: Read-only user role. * `USER_MAP_ONLY`: User cannot do anything except for looking at the map. Useful for on-vehicle displays in shared vehicles. For vehicle (access) roles, these include: * `VEHICLE_OWNER`: Owner of the vehicle. * `VEHICLE_USER`: User of the vehicle - the same as OWNER in terms of access, but without admin rights, such as to add or remove other users. * `VEHICLE_MAINTAINER`: Person responsible for the maintenance of the vehicle. * `VEHICLE_MANUFACTURER`: Person responsible for the manufacturing of the vehicle. * `VEHICLE_MANUFACTURER_UPLOAD`: Person responsible for the manufacturing of the vehicle (can upload data for this vehicle). * `VEHICLE_READ_ONLY`: Person can only observe the data of the vehicle, but cannot edit anything. * `VEHICLE_NO_DETAIL_NO_EDIT`: User can not see details of trips nor edit vehicle profile. * `VEHICLE_ONLY_CURRENT`: User can not see anything except the current position and data. * `VEHICLE_UPLOAD_DATA`: Vehicle can upload data. Used for API keys. * `VEHICLE_OWNER_GROUP_FOLLOWER`: Owner of a vehicle, but many functions are disabled to make it clear a vehicle is part of a group (and only the group leader can be used for common tasks, such as notes, documents, etc.). For organization roles, these include: * `USER_ORG_STANDARD`: Standard user org access role * `USER_ORG_ADMIN`: Admin user org access role * `USER_ORG_READ_ONLY`: Read-only user org access role * `USER_ORG_SERVICE`: Service user org access role * `USER_ORG_MARKETING`: Marketing user org access role * `USER_ORG_ENGINEER`: Engineer user org access role ## Permission Auditing and Compliance The platform maintains comprehensive audit trails for all permission-related activities. Audit trail components include permission grants and revocations with timestamps and responsible parties, role assignments and modifications including custom role changes, access attempts and authorization decisions for compliance monitoring, and administrative actions affecting permissions and roles. Compliance features include data access logging for regulatory compliance (GDPR, CCPA, etc.), permission reports for organizational audits, access certification workflows for periodic reviews, and automated alerts for unusual permission patterns. # Auth and security Source: https://docs.ctechnology.io/developer/platform-basics/security Understanding the security architecture and access control relationships in the c.technology platform The c.technology platform implements a comprehensive security model that governs how organizations, users, and vehicles interact within the system. This security architecture ensures appropriate data access, maintains clear audit trails, and supports complex multi-tenant scenarios while preserving data isolation and privacy. ## Security architecture overview The platform's security model is built on three fundamental entity types that work together to provide granular access control: 1. **Organizations** - Multi-tenant containers that group users and vehicles. 2. **Users** - Individual accounts with authentication and authorization. 3. **Vehicles** - IoT-enabled assets with sensor data and operational information. These entities are connected through a role-based access control (RBAC) system that determines what actions users can perform on vehicles, either directly or through their organizational memberships. ## Core security relationships The platform implements several key relationship models that define access patterns and data sharing boundaries: ### Organization - vehicle relationships Organizations can be associated with vehicles through the `OrganizationVehicle` model, which defines the nature of the organization's relationship with each vehicle. These relationships include OEMs that manufacture vehicles, dealer organizations that sell or distribute vehicles, service provider organizations that maintain or repair vehicles, and fleet owner organizations that operate multiple vehicles commercially. Each organization-vehicle relationship includes a specific role that determines what actions the organization and its members can perform on that vehicle. ```python theme={null} # Example organization-vehicle relationship { "organization": "com.bostonwhaler", "vehicle": "boat-12345", "role": "VEHICLE_MANUFACTURER" } ``` ### User - vehicle relationships Users can have direct access to vehicles through the `UserVehicleAccess` model, which assigns specific roles for individual user-vehicle combinations. This mechanism supports scenarios such as vehicle ownership where users register and own their personal vehicles, family sharing where vehicle owners grant access to family members, professional services where mechanics or inspectors need temporary access, and emergency access for support or rescue scenarios. The direct access model takes precedence over organizational access, allowing fine-grained control over individual permissions. ### Organization - user relationships Users become members of organizations through the `OrganizationMember` model, which defines their role within that organization. Organization membership provides inherited vehicle access based on the organization's vehicle relationships, administrative capabilities for managing the organization's vehicles and members, billing and subscription management responsibilities, and custom role definitions specific to the organization's operational needs. ## Multi-tenant data isolation The platform ensures logical data isolation between different organizational contexts while enabling controlled data sharing when appropriate: ### Tenant boundaries Each organization operates within its own logical tenant space, with clear boundaries around user data where organization members only see users within their organization context, vehicle data with access limited to vehicles the organization has relationships with, configuration data with custom settings and preferences isolated per organization, and billing data with financial information completely separated by organization. ### Cross-tenant scenarios The platform supports controlled cross-tenant interactions for legitimate business scenarios including multi-OEM vehicles where vehicles may have relationships with multiple manufacturers, service provider access where maintenance organizations need temporary vehicle access, data sharing agreements between partner organizations, and white-label deployments where one organization provides services to others. ### Primary organization relationships Users and vehicles can have primary organization relationships that determine default contexts and billing responsibilities. User primary organization influences UI branding, default features, and support routing, while vehicle primary organization determines billing responsibility and primary management authority, and manufacturing organization affects device configuration, firmware updates, and technical support. ## Access control mechanisms The platform implements several layers of access control to ensure appropriate data access. See the [permission section](/developer/platform-basics/permission) for detailed information. ## Authentication and session management Authentication is handled through secure token-based mechanisms. Tokens can be retrieved by logging in with email and password, using OAuth or SAML for third-party integrations, or through API keys for programmatic access. # Subscriptions Source: https://docs.ctechnology.io/developer/platform-basics/subscription Understanding subscription models, billing, and feature access in the c.technology platform The c.technology platform operates on a subscription model that enables flexible access to services while supporting various business models including individual ownership, organizational fleet management, and OEM partnerships. The subscription system provides granular control over feature access, billing arrangements, and service delivery across the platform. ## Subscription architecture The platform's subscription system is built around three core models that work together to provide flexible service delivery: 1. **ServiceSubscription** - Individual subscriptions that grant access to specific services. 2. **SubscriptionPackage** - Bundled offerings for organizations with multiple vehicles. 3. **Billing Integration** - Payment processing through Stripe, vouchers, and organizational billing. This architecture supports both individual consumer subscriptions and complex B2B arrangements with custom pricing, revenue sharing, and white-label deployments. ## Organizational billing For B2B subscriptions, the platform has an integrated organizational billing system that manages invoicing, payment processing, and subscription lifecycle management at the organization level. At the end of each billing cycle, the platform generates invoices based on the organization's active subscriptions and vehicle count, which can be paid through various methods including credit card, bank transfer, or prepaid budgets. These invoices are autmatically balanced against all partner organizations in the system to ensure accurate revenue sharing and cost allocation. # Trips Source: https://docs.ctechnology.io/developer/platform-basics/trip How to manage and utilize trip data within the c.technology platform. Trips represent longer "actions" during which a vehicle is in motion, typically starting with an ignition on or engine start event and ending with an ignition off or engine stop event. If no ignition data is available, the c.technology system can automatically detect trips based on movement and speed thresholds. Trips are segmented into shorter sections called "triplegs" based on changes in speed, or other significant events. Together with vehicle actions, trips make up the logbook of a vehicle. ## Trip structure A trip is structured as follows: ```json theme={null} { "id": "trip_01k5bb7jgdfbmvj20fjz261p75", // Unique trip ID in TypeID format. "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43", // The vehicle the trip is associated with. "timestamp_start": "2025-09-17T07:36:52.078000+0000", // Start time of the trip. "timestamp_end": "2025-09-17T12:21:49.566000+0000", // End time of the trip. "completed": false, // Indicates if the trip has been completed (ended with ignition off). "deleted": false, "valid": true, "validation_score": 0.9795778132487861, // Confidence score of the trip's validity (0.0 to 1.0). "name": null, // Optional user-supplied name for the trip. "driver": null, "notes": null, "fuel_manual_lt": null, "image_rect_url": "...", // URL to a rectangular image representing the trip (e.g. map snapshot). "speed_max": 16, "speed_avg": 8.704024183580822, "distance_tot": 19456.237482334018, "distance_tot_gps": 19456.237482334018, "distance_tot_can": null, "distance_tot_odo": 0, "duration_tot": 7505.23, "duration_cruising": 7016.248999999999, "fuel_start_level_pct": null, "fuel_start_level_lt": null, "fuel_most_recent_pct": null, "fuel_most_recent_vlt": null, "fuel_used_pct": null, "fuel_used_lt": 0, "fuel_num_refueled": null, "fuel_refueled_pct": null, "fuel_refueled_lt": null, "fuel_avg_lt_per_100km": null, "battery_start_level_volt": 13.539857142857143, "battery_end_level_volt": 13.345333333333334, "start_energy_available_ah": null, "end_energy_available_ah": null, "continuous_energy_consumption_ah": null, "start_energy_available_wh": null, "end_energy_available_wh": null, "continuous_energy_consumption_wh": null, "start_energy_available_pct": null, "end_energy_available_pct": null, "continuous_energy_consumption_pct": null, "n2k_operation_hours_tot": 7380, "can_fuel_consumption_avg": null, "can_fuel_consumption_max": null, "can_fuel_consumption_tot": null, "can_rpm_max": null, "can_rpm_avg": null, "visibility": "PRIVATE" } ``` A trip may be classified as "invalid" if it was detected via automatic GPS data analysis, but does not meet certain criteria (e.g. minimum distance or duration, or contains many GPS outliers). The path of a trip can be retrieved by querying the associated triplegs: ```bash theme={null} curl -X GET https://api.ctechnology.io/api/v2.2/trip/{trip_id}/path?fields=timestamp,latitude,longitude,altitude,speed&simplify=true \ -H "Authorization: Token {access_token}" ``` Adding `&simplify=true` will reduce the number of points in the path while maintaining its overall shape, which is useful for visualization. # Users Source: https://docs.ctechnology.io/developer/platform-basics/user How user accounts are structured and managed within the c.technology platform. Users represent individual accounts within the c.technology platform who can authenticate, access vehicles, and interact with the system. The platform offers an email-based authentication system without optional OAuth and SAML login capabilities, designed to provide seamless access across web applications, mobile apps, and API integrations. Users can belong to multiple organizations, giving them control over organizational aspects and vehicles under management. > [!NOTE] > > User and organization access to vehicles may be controlled fine-grained through roles and permissions. See the [permissions](/developer/platform-basics/permission) section for more details. ## User structure Users are structured as follows: ```json theme={null} { "id": "usr_01jnk61cv5ev1a1ty1136gfwh6", // Unique user ID in TypeID format. "email": "demo@ctechnology.io", // The user's email address, used for login and communication. // An email address is always unique and commonly used for user identification throughout the platform. "first_name": "Demo", "last_name": "User", "address_street": "", "address_city": "", "address_zip": "", "address_country_code": "", "profile_picture_id": null, "profile_picture_url": "...", // Various user settings. "primary_locale": "en-US", "measurement_units": "METRIC", "time_format": "24H", // Settings for different applications, stored as JSON blobs for frontend customization. "settings_webapp": { "main_role": "PRIVATE", "selected_theme_id": "com.demoCompany.theme.mcycle", "current_organization": "com.demoCompany", "professional_sidebar_filter_vehicles": { "show_own_vehicles": true, "show_client_vehicles": true } }, "settings_nativeapp": { "theme": "io.ctechnology.theme.light" }, // Notification and outreach preferences. "may_use_email_for_marketing": false, "notification_new_message": true, "notification_new_news_article": true, "ecosystem_timestamp_last_news_read": "2025-08-28T09:00:22.117Z" } ``` A user can belong to a "primary organization" that influences their default experience throughout the platform. Commonly, this is a vehicle manufacturer, but it may also be a dealership, fleet operator, or other organization. ## Data privacy and compliance In accordance with various data protection regulations, users have control over their personal data and privacy settings. This includes options to manage email preferences, data sharing consents, and the ability to request data deletion or export. # Vehicles Source: https://docs.ctechnology.io/developer/platform-basics/vehicle Comprehensive explanation of vehicles and their role within the c.technology platform. Vehicles are the core entities within the c.technology platform, representing physical assets - potentially equipped with IoT devices that collect and transmit real-time data. ## Vehicle types Given c.technology's origin in the powersports and marine industries, the platform is designed to accommodate a wide variety of vehicle types: * `BOAT`: Boats and watercraft of all sizes and types, from small personal watercraft to large yachts. * `MCYCLE`: Motorcycles, including cruisers, sportbikes, touring bikes, and off-road motorcycles. * `EBIKE`: Electric bicycles, including pedal-assist and throttle-controlled models. * `CLASSCAR`: Classic cars, vintage vehicles, and collector automobiles. * `MOTOR`: Individual motors or engines, such as outboard motors, inboard engines, or standalone power units. > [!NOTE] > > The list of supported vehicles is continuously expanding as the platform evolves to meet the needs of diverse industries and use cases. Similarly, each vehicle type can be associated with different drivetrain types: * `GASOLINE`: Traditional internal combustion engines powered by gasoline. * `DIESEL`: Engines powered by diesel fuel, commonly used in larger vehicles and commercial applications. * `ELECTRIC`: Fully electric vehicles powered by batteries and electric motors. ## Vehicle identification and metadata Vehicles contain multiple identification methods to support various operational scenarios. * **UUID**: Each vehicle is assigned a globally unique identifier (UUID) upon creation, ensuring uniqueness across the entire platform. This UUID is usually presented in [TypeID](https://github.com/jetify-com/typeid) format, such as `veh_01jnk61e5pf6zs5ag6483xqe43`. * **Device ID**: Each vehicle is assigned a manufacturer-specific short device ID that can be used by customers for convenience. * **VIN**: The Vehicle Identification Number (VIN) is used for official vehicle registration or as a manufacturer serial number. * **Vehicle Registration ID**: This is typically the license plate number or registration number assigned by governmental authorities. * **Organization-specific IDs**: Organizations can assign custom IDs to vehicles for internal tracking and management purposes. Additional metadata includes: * **Name**: A user-friendly name for easy identification. * **Description**: A text field for additional details about the vehicle. * **Category, Family, Type**: Organizational metadata that allows grouping and classification of vehicles based on predefined categories, families, and types. * **Installable Parts**: A list of parts that can be installed on the vehicle, each with its own metadata and tracking capabilities. The most important data fields of a vehicle look as follows: ```json theme={null} { "brand": "Demo Brand", // May be used if no organization vehicle type is set. "delivery_date": "2025-03-04 12:56:09.654672+00:00", "desc": "No description given", "development_vehicle": false, // Indicates if this is a development/test vehicle with additional capabilities. "device_id": "123456789", // Manufacturer-specific short device ID. "drivetrain_type": "DIESEL", "group_id": null, "id": "veh_01jnk61e5pf6zs5ag6483xqe43", // Unique vehicle ID in TypeID format. "image_id": "img_01jnk61e73fnabjaq8c15he5za", "image_url": "...", "initial_date": "2024-06-23", "initial_distance": 1966482, "initial_operation_hours": 5742000, "initialization_complete": false, "manufacturing_organization_id": null, // The organization that manufactured this vehicle. "name": "Demo Boat 1", "primary_organization_id": "com.demoCompany", // The organization covering the subscription costs. "type": "Viper CB1", // May be used if no organization vehicle type is set. "vehicle_identification_number": "544-0227-680", "vehicle_registration_id": "", "vehicle_type": "BOAT", "hardware_type": "FMC640", "protocol_type": "TELT_COD_8", "sim_type": "1NCE", "organization_vehicles": [ // List of organizational relationships, the manufacturing organization should be included here. { "organization_id": "com.demoCompany", "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43", "primary_organization": true, "role": "VEHICLE_MANUFACTURER", "organization_vehicle_id": "123456789", // Organization-specific vehicle ID. "organization_vehicle_name": "544-0227-680", // Organization-specific vehicle name. "location_main_desc": "", "vehicle_category_id": "vcat_01jnk61e3vf4p98dt238eesmj1", "vehicle_category_name": "Boats", "vehicle_family_id": "vfam_01jnk61e42e9dtxf4wbcs4qzwg", "vehicle_family_name": "Boats with combustions engine", "vehicle_type_id": "vtpe_01jnk61e4ef1d9jexfn6h29gg8", "vehicle_type_name": "Viper CB1" }, ... ], ... } ``` ## Vehicle Groups and Multi-Component Systems The platform supports vehicle groups for managing multi-component systems that should be presented as unified entities to end users. This feature enables trailer and tow vehicle combinations, multi-engine vessel configurations, modular vehicle systems with separate monitoring units, and fleet coordination for related vehicles. Group members share certain operational characteristics while maintaining individual sensor data and status information. A vehicle's group is given in the `group_id` field. More information about groups can be retrieved by querying: ```bash theme={null} curl -X GET https://api.ctechnology.io/api/v2.2/vehicle-group/{group_id} \ -H "Authorization: Token YOUR_TOKEN" ``` # Vehicle actions Source: https://docs.ctechnology.io/developer/platform-basics/vehicle-action How to read and use vehicle actions within the c.technology platform. Vehicle actions are points in time where a specific and significant action or event has occurred on a vehicle. This may range from rather mundane actions such as "ignition on" or "engine start" to more complex actions such as "filling in a checklist", "leaving the home location", or "starting a trip". ## Action structure A vehicle action is structured as follows: ```json theme={null} { "id": "vact_01k51vkrmwenprvcz87vs80z4c", // Unique vehicle action ID in TypeID format. "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43", // The vehicle the action is associated with. "user_id": null, "trip_id": null, // The trip the action is associated with, if any. "timestamp": "2025-09-13T15:37:57.785Z", // Time the action occurred. "type": "IGNITION_ON", // The type of action, see list below for common types. "data": { // Additional data associated with the action, varies by action type. "external_voltage": 13117 }, "message": "Demo Boat 1 had its ignition turned on." // A human-readable message describing the action. } ``` # Vehicle commands Source: https://docs.ctechnology.io/developer/platform-basics/vehicle-command How to remotely control and configure vehicles through the c.technology platform. Vehicle commands are used to remotely control and configure vehicles through the c.technology platform. They include actions such as locking/unlocking doors, reconfigurations of transmission intervals, etc. ## Command structure Commands are structured as follows: ```json theme={null} { "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43", // The vehicle the command is targeted at. "timestamp_created": "2025-09-17T12:21:49.566Z", // Time the command was created. "timestamp_planned_execution": "2025-09-17T12:25:00.000Z", // Optional time the command should be executed. "priority": "HIGH", // Priority of the command: LOW (delivery when possible), HIGH (immediate delivery). "command": "DOUT1:ON", // The command to be executed, format depends on the command type. "timestamp_execution": null, // Time the command was executed, null if not yet executed. "response": null, // Response from the vehicle after execution, null if not yet executed. } ``` Commonly, IoT devices in vehicles only communicate at certain intervals to save power and data costs. Thus, most commands are sent with `LOW` priority, and queued and delivered when the vehicle next connects to the platform. Commands with `HIGH` priority are delivered immediately when the vehicle connects, interrupting regular data transmission if necessary. > [!NOTE] > > It may not be possible for you to send `HIGH` priority commands depending on your vehicles, IoT devices, and subscription plan. # Vehicle data Source: https://docs.ctechnology.io/developer/platform-basics/vehicle-data Understanding vehicle data models, sensor configurations, and real-time status monitoring within the c.technology platform. Vehicle data (telemetry) is respresented through two extensible models: Vehicle updates and vehicle statuses. ## Vehicle update Vehicle updates represent the raw data ingested from a vehicle, including sensor readings, location information, and system parameters. Generally, you will only have to interact with the VehicleUpdate model when uploading data from a vehicle (see [data upload guide](/developer/getting-started/data-upload) for details). ## Vehicle status Vehicle status information represents fully sanitized and augmented data about a vehicle's current state, including location, fuel levels, battery status, and other operational parameters. This data is derived from raw vehicle updates and is made available through the VehicleStatus model: ```json theme={null} { "timestamp": "2025-09-17T12:21:49.566Z", // Time of the status record "last_update": "2025-09-17T12:21:49.566Z", // Time of the last received vehicle update "status": "PARK_HOME", // Operational status: SETUP, PARK, PARK_HOME, FLOATING, CRUISING "fuel_level_pct": 0, "fuel_level": 0, "expected_range": null, "remaining_energy_wh": null, "remaining_energy_ah": null, "state_of_charge_pct": null, "battery_main_pct": 100, "battery_main_voltage": 13.345333333333334, "battery_main_trend": "CHARGE", "battery_main_trend_slope": 20.518, "battery_ext_1_pct": 71.56935817805379, "battery_ext_1_voltage": 26.76133333333333, "battery_ext_1_trend": "CHARGE", "battery_ext_1_trend_slope": 0.781, "battery_ext_2_pct": null, "battery_ext_2_voltage": null, "battery_ext_2_trend": null, "battery_ext_2_trend_slope": null, "battery_ext_3_pct": null, "battery_ext_3_voltage": null, "battery_ext_3_trend": null, "battery_ext_3_trend_slope": null, "battery_ext_4_pct": null, "battery_ext_4_voltage": null, "battery_ext_4_trend": null, "battery_ext_4_trend_slope": null, "speed": 0, "total_odometer": null, "pdop_value": 10, "last_valid_location_update": "2025-09-17T12:21:49.566Z", // Time of the last valid GPS location "distance_to_shore": 39.98442664031744, "shore_zone": "OPEN_SEA", "temp_1": 33.25, "temp_2": 27.93, "temp_3": 30, "temp_4": 26.87, "sensor_temp_1_state": "G", "sensor_temp_2_state": "G", "sensor_temp_3_state": "G", "sensor_temp_4_state": "G", "sensor_relative_humidity_1_pct": 0, "sensor_relative_humidity_2_pct": 0, "sensor_relative_humidity_3_pct": 0, "sensor_relative_humidity_4_pct": 0, "sensor_relative_humidity_1_state": "G", "sensor_relative_humidity_2_state": "G", "sensor_relative_humidity_3_state": "G", "sensor_relative_humidity_4_state": "G", "sensor_battery_1_pct": 0, "sensor_battery_2_pct": 0, "sensor_battery_3_pct": 0, "sensor_battery_4_pct": 0, "temp_motor": null, "temp_water": null, "landline_voltage": 220, "in_water": null, "din_1_state": true, "din_2_state": true, "din_3_state": false, "din_4_state": null, "din_5_state": null, "ignition_on": true, "is_locked": null, "dout_1_state": null, "dout_2_state": null, "dout_3_state": null, "dout_4_state": null, "dout_1_waiting_for_update": null, // Indicates if the output state change is pending "dout_2_waiting_for_update": null, "dout_3_waiting_for_update": null, "dout_4_waiting_for_update": null, "active_geofences": [], // List of active geofences "vehicle_status_can": null, // CAN bus data, if available "vehicle_status_n2k": { // NMEA2000 data, if available "n2k_last_update": "2025-09-17T12:21:49.566Z", "n2k_engine_1_seconds": 4286880, "n2k_engine_1_seconds_last_update": "2025-09-17T12:21:49.566Z", ... }, "vehicle_status_obd2": null, // OBD2 data, if available "longitude": 9.5582564, "latitude": 47.4984334, "altitude": 404, "angle": 180, "fuel_level_voltage": 3.6666999999999996, "temp_1_trend": "CONST", "temp_2_trend": "INCR", "temp_3_trend": "CONST", "temp_4_trend": "INCR", "distance_to_home": 0, "fuel_last_update": "2025-09-17T12:21:49.566Z", // Time of the last fuel level update "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43" // Associated vehicle ID } ``` The most up-to-date status of a vehicle can be retrieved by querying: ```bash theme={null} curl -X GET https://api.ctechnology.io/api/v2.2/vehicle/{vehicle_id}/status \ -H "Authorization: Token {access_token}" ``` Similarly, the most recent status is always broadcasted via the AsyncAPI WebSocket interface (see [AsyncAPI documentation](/asyncapi-reference/introduction) for details) upon connection and whenever a new status is available. # Vehicle errors Source: https://docs.ctechnology.io/developer/platform-basics/vehicle-error How the c.technology platform handles vehicle error detection, reporting, and diagnostics. Vehicle errors are representations of (timestamped) fault conditions detected in vehicles, reported through the VehicleError model. Errors are matched with [error definitions](/handbook/oem/engineering#error-management) whenever possible. ## Vehicle error structure A vehicle error has the following structure: ```json theme={null} { "id": "verr_01jv4nr7n4f6bbty91fagdwn83", // Unique vehicle error ID in TypeID format. "vehicle_id": "veh_01jnk61e5pf6zs5ag6483xqe43", // The vehicle the error is associated with. "error_definition_id": "errdef_01jnk621baffebddn635bnwwmc", // The matched error definition ID, if available. "ticket_ids": [], "status": "OPEN", // Status of the error: OPEN, CLOSED "timestamp_opened": "2025-05-13T11:15:58.000000+0000", "timestamp_closed": null, "device_id": null, "error_code": null, "error_code_user": "BAT-LOW", "revision": "1.1", "device_category_id": "VEHICLE", "severity": "ERROR", "notification_priority": "HIGH", "extra_info": null } ``` The data may be supplied by the error ingestion mechanism (via IoT device or HTTP endpoints), or automatically added from the respective error definition. # Application purposes Source: https://docs.ctechnology.io/handbook/interactions How the different applications and users interact within the c.technology platform. ## Cloud platform management for OEMs Vehicle manufacturers use our comprehensive web dashboard to oversee their entire vehicle fleet, analyze customer behavior patterns, and manage the complete vehicle lifecycle from production to end-of-life. ![OEM web dashboard showing vehicle fleet overview with performance metrics](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/dashboard.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=a216dd761e986f6768ac0736758efab0) OEMs use the following functionality: * **Vehicle management**: Real-time dashboards showing vehicle performance, usage patterns, and health metrics across the entire production portfolio. * **Maintenance and documentation**: Comprehensive maintenance records, service history, and technical documentation (incl. service manuals and checklists) for each vehicle. * **Customer management**: Tools for managing relationships with vehicle owners, including communication, support, and service coordination. * **Partner network**: Management of dealer networks and service provider partnerships, including vehicle assignments and support escalation. * **Data analytics**: Advanced reporting on vehicle performance, customer satisfaction, and market trends. * **Engineering support**: Feedback loops and over-the-air updates for engineering teams to optimize vehicle design and performance based on real-world data. ## Fleet, operations, and general management for professional partners Professional partners including dealers, service providers, and fleet operators use our web interface to manage customer vehicles and optimize their operations. ![Professional web dashboard showing customer vehicle management interface](https://mintcdn.com/ctechnologyag/2fKpZfAzamlnzOS6/images/handbook/professional/dashboard.png?fit=max\&auto=format\&n=2fKpZfAzamlnzOS6\&q=85\&s=ff0e3ae874f5355f359c8b18a8165581) Their core functionality includes: * **Customer vehicle management**: Complete oversight of customer-owned vehicles including service history and maintenance scheduling. * **Service management**: Tools for scheduling, tracking, and documenting vehicle service and maintenance activities. * **Business analytics**: Performance metrics, service efficiency reports, and customer satisfaction tracking. * **Vehicle services**: Specialized tools for different types of vehicle services and maintenance procedures. * **Communication hub**: Direct communication channels with vehicle owners for service coordination and updates. ## Android / iOS apps for vehicle owners Individual vehicle owners use our mobile applications to interact with their vehicles and access platform services. ![Mobile app showing private vehicle owner dashboard with key metrics and navigation](https://mintcdn.com/ctechnologyag/2fKpZfAzamlnzOS6/images/handbook/private/dashboard.png?fit=max\&auto=format\&n=2fKpZfAzamlnzOS6\&q=85\&s=cb5067cd362309dcabe1c6f6b41d575a) This includes in particular: * **Dashboard**: Overview of vehicle status, key metrics, and alerts, plus access to various applications to manage their vehicle and its ecosystem. * **Vehicle cockpit**: Real-time vehicle status, location tracking, and performance monitoring. * **Digital logbook**: Automated trip logging, fuel consumption tracking, and usage statistics. * **Maintenance management**: Service reminders, maintenance history, and scheduling tools. * **Notes & documentation**: Personal notes, photos, and documentation storage for each vehicle, including access to OEM documentation. * **Notifications**: Real-time alerts for vehicle status, maintenance needs, and security events. * **Subscription management**: Access to premium features and service subscriptions. * **IoT device integration**: Connection and management of installed tracking and monitoring devices. ## Switching between roles If you are part of an organization (either an OEM or a professional), you can always still use your account from a "private perspective" to access your personal vehicles. To switch between your organizational role and your private role, click on the respective icon next to your profile picture in the top right corner. ![Mobile app showing role switching interface for multiple organization access](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/dashboard_switch_roles.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=fcbdb34e936b9d9c25a3dbf31e14beaa) If you are part of multiple organizations, you can switch between these organizations in the same way. # Govecs Digital (eSchwalbe) Source: https://docs.ctechnology.io/handbook/oem-app/govecs-digital Additional information specific to the Govecs Digital (eSchwalbe) application. ## Onboarding The Govecs Digital app is specifically designed for Govecs eSchwalbe scooters. The following scooters are supported as of Fall 2025: * Govecs eSchwalbe 45 (max. 45 km/h) * Govecs eSchwalbe 70 (max. 70 km/h) ## Troubleshooting > **Unlocking unresponsive** > > It may happen that your scooter does not respond to unlock commands from the app immediately. > This is often due to longer periods of storage in environments with poor cellular reception. > **Wrong position on map** > > The position of your scooter may be inaccurate due to the following reasons: > > 1. The scooter's GPS module has not yet acquired a proper satellite fix. This can take several minutes. > 2. The scooter has not been used for a while and a backlog of GPS data needs to be transmitted to the app before the current position can be updated. > 3. The scooter is wrongly configured. # Torqeedo TorqView Source: https://docs.ctechnology.io/handbook/oem-app/torqview Additional information specific to the Torqeedo TorqView application. ## Onboarding As Torqeedo motors can connect via Bluetooth to the TorqView app, the onboarding process includes an additional step to pair your motor with the app. Not only does this ensure you are properly set up, it will also associate the motor with your TorqView account, and synchronize all its components with the app for easier management, maintenance and support. ## Bluetooth To connect your Torqeedo motor to the TorqView app, ensure that Bluetooth is enabled on your mobile device. To connect, simply click on the red "Connect" button on the dashboard screen of the app. The app will search for available Torqeedo motors in the vicinity. Once your motor appears in the list, select it to initiate the pairing process. You may be prompted to enter a PIN or confirm a code displayed on both the motor and the app to complete the pairing. ## Firmware updates The TorqView app allows you to easily check for and install firmware updates for your Torqeedo motor. To check for updates, navigate to the "Settings" section of the app and select "Vehicle parts". If an update is available, follow the on-screen instructions to download and install it. Ensure that your motor remains powered on and within range of your mobile device during the update process to avoid any interruptions. ## Maintenance and diagnostics The TorqView app automatically logs and shows you all alerts and error codes generated by your Torqeedo motor. To view these, click on "Errors" on the dashboard. # Channels Source: https://docs.ctechnology.io/handbook/oem/channels How to manage news, push notifications, and support. The Channels section manages customer and partner communication through news articles, push notifications, and support interactions. ## News articles You can create and manage news articles to share updates, announcements, and important information with your customers and partners. These news articles are shown in the Private App in the "News" section, and in the main dashboard in the Professional Hub. News articles are shared by default with anyone who has access to any of your vehicles. > [!NOTE] > > Professional partners can add their own news articles, which will then be visible to their customers in the Private App and to you in the Professional Hub. ![OEM dashboard showing news articles management interface](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/news_articles.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=658dfffcc835b32ec56ad34d3b2aa911) Clicking on an article opens its details view, where you can edit the article's content, tags and images. Use the tags to categorize articles (e.g., "Maintenance", "Product Updates", "Safety Alerts"). For the article content, you can use [Markdown](https://www.markdownguide.org/basic-syntax/) formatting. ![OEM dashboard showing news article details with editing interface](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/news_article_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=d8ab097c42065fef8e7bcaafa78f4263) The preview on the right shows how the article will look in any of the apps. For convenience, you can directly "Create a push notification" from the article view to notify customers about important news. ## Push notifications Using push notifications, you can send targeted messages directly to your customers' devices. > [!NOTE] > > Currently, you can only send push notifications to *all* your customers at the same time. In future releases, more granular targeting options will be available. To create a new push notification, click the "Create push notification" button. ![OEM dashboard showing push notification management interface](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/push_messages.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=ab98500895531ca391be3105a26c7b2d) A push message consists of a short title, and a longer message body. Make sure you keep these concise, as they will be displayed in the notification tray of the mobile devices. ![OEM dashboard showing individual push notification creation form](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/push_message_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=c6dc35bd02a7aa07f399a00a19346ced) In the details tab, you can see how many customers your push notification will reach, and upon sending it to how many devices it was successfully delivered. > [!NOTE] > > Push notification delivery depends on various factors outside of your control, such as device settings, network availability, etc. Therefore, not all devices may receive the notification, and delays may occur. ## Support The support tab provides a centralized interface to manage customer support requests and interactions. Support is centered around **tickets** and **chats**. Tickets are used to group issues of a customer, and may have a chat associated with them (for easier and more real-time communication). ![OEM dashboard showing customer support ticket management interface](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/tickets.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=c92944ca565f35468eb2b3ca31840f06) Clicking on a ticket opens its details view, where you can see all relevant information about the issue, its status, and the associated chat (if any). ![OEM dashboard showing individual support ticket details and response interface](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/ticket_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=8215619970d66ed058dffc208fb32fd7) Clicking on the vehicle, user, or chat takes you directly to the respective [vehicle details view](/handbook/oem/vehicle#vehicle-details), [user details view](/handbook/oem/ecosystem#customer-management), or chat view. In the chat view, you can see the entire conversation history and respond to customer messages. > [!NOTE] > > Note that depending on your organization's support settings, tickets may be managed by your partners, or the opening of tickets by customers is restricted. # Documents and checklists Source: https://docs.ctechnology.io/handbook/oem/documents Manage and share documents, handbooks, checklists, etc. For both documents and checklists you can create, edit, and manage them in this part of the OEM Suite. Both can then be shared with a subset of vehicles: only your own, vehicles of certain families, types or categories, or even individual vehicles. For example, you can upload user manuals, service guides, warranty information, and technical documentation as documents. Users of the Professional Hub and Private App can then immediately access the respective documents. ## Documents Documents currently support PDF files and images up to 16MB in size. They are organized by category and can be associated with specific vehicle models or made available globally. ![OEM dashboard showing document management interface with categories and upload options](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/note/documents.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=fe30634ae951593a43ac0ed51f29b073) In additional to uploading the document itself, you can specify the language it is in, as well as provide translations for the name. The translations will be shown to the user based on their language settings in the app. To change the translation, click on the *language* icon next to the name field. ![OEM dashboard showing document details form with language and translation settings](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/note/document_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=742f506b69e922913d4185f6fdd75904) The following categories of documents are available: * **Manuals**: User manuals and operating instructions * **Maintenance booklets**: Service guides and maintenance schedules * **Identification documents**: Registration papers and certificates * **Inventories**: Parts lists and component catalogs * **Others**: Miscellaneous documents relevant to vehicle owners and service providers ![OEM dashboard showing document sharing settings with vehicle assignment options](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/note/document_sharing.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=1216cae4d79bff16ae2832febac3948f) Documents can be kept private or shared with specific vehicles, *all* vehicles, or individual types, families or categories. When choosing specific vehicles, you can use the search field to find vehicles by their name or VIN. ## Checklists Checklists are structured lists of tasks or procedures that can be assigned to vehicles. Upon completion, a checklist is stored in the vehicle's history and can be reviewed by OEMs, professional partners, or vehicle owners. \[!WARNING] The action of *completing* a checklist is stored immutably and cannot be modified or deleted. ![OEM dashboard showing checklist management interface with task lists](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/note/checklists.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=01ee27d505be5c631626d5e34ca1398c) To add points to a checklist, simply click on the **add point** button. You can then directly edit the point itself, and rearrange points by dragging and dropping them. ![OEM dashboard showing checklist details editor with drag-and-drop task points](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/note/checklist_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=77344910c29d132901c26bd8f3a2dcd9) All checklists and points can be translated into multiple languages. To change the translation, click on the *language* icon next to the name field. A checklist is always shown in the language of the user completing it, falling back to the default language if no translation is available. Similarly to documents, checklists can be kept private or shared with specific vehicles, *all* vehicles, or individual types, families or categories. When choosing specific vehicles, you can use the search field to find vehicles by their name or VIN. # Ecosystem Source: https://docs.ctechnology.io/handbook/oem/ecosystem Managing your partners and customers / vehicle owners. The Ecosystem section manages your network of business partners including dealers, service centers, and customers who interact with your vehicles. ## Partner management When navigating to the Ecosystem section, you will first see the **Partners** tab. ![OEM dashboard showing partner management interface with dealer and service provider network overview](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/partners.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=3c38d8f17d9cb0fb443ded40a758ad8d) This tab lets you manage all your business partners, including dealers, service providers, and other OEMs. Partners can be assigned vehicles, allowing them to access and manage those vehicles based on their role (e.g., dealer or service provider). Click on "Add partner" to create a new partner organization. You can also import multiple partners at once using the "Import from CSV" button. Clicking on any partner in the list opens its details view. ![OEM dashboard showing partner details form with contact information and management settings](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/partner_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=769c48de1c886dffafb43145ef356ae1) Each individual partner can be assigned a name, address, contact details, etc. \[!WARNING] You can only edit this information as long as the partner has not been "claimed" yet. Once you are content with the partner information, you can send an invitation email to the partner by clicking the "Send invitation" button. The partner can then claim the organization and create their own user account. ![OEM dashboard showing vehicle assignment interface for partner organizations](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/partner_add_vehicle.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=6e6ee009d4101c384ee8e01ee0c33771) Finally, you can assign vehicles to the partner (this can be done even after the partner has claimed the organization). Click on "Add vehicles" to open a dialog where you can select vehicles to assign to the partner. ## Customer Management In the "Owners" tab, you can manage your customers who own vehicles registered in your system. Initially, a table with all vehicle owners is shown. This table includes basic information about each owner and the vehicles they own, as well as a contact button to reach out to them directly. ![OEM dashboard showing customer management interface with vehicle owner contact information](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/owners.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=c56a04b1fdf1f80da6432ce225b8124b) Clicking on an owner opens their detailed view. For each owner, you see basic information (name, email), you can assign private information only visible to you (organization user id, name, and description), and see which vehicles they have access to. ![OEM dashboard showing customer details with comprehensive vehicle fleet and contact information](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/owner_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=077dcb344ce35b559112b7b21c4e7934) Clicking on any vehicle takes you directly to the respective [vehicle details view](/handbook/oem/vehicle#vehicle-details). # Engineering Source: https://docs.ctechnology.io/handbook/oem/engineering Management of IoT devices, error definitions, and OTA firmware updates. The Engineering section provides tools for managing maintenance schedules, error definitions, and firmware updates across your vehicle fleet. ## IoT devices management The IoT devices tab allows you to manage all IoT devices that are connected to your vehicles. \[!NOTE] This section primarily applies to you if you purchased IoT devices from us as part of our OEM solution. If you are using your own devices, you may not need to use this section. The intial list shows all IoT devices under your organization, including their status, device ID, and the vehicle they are assigned to (if any). You can add new devices by clicking the "Add IoT device" button. This opens a dialog where you can enter the device ID of the new device. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/iot_devices.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=61e3b569e151d01cb46ee733ec081b08) An IoT device's detail view shows more information about the device, including its status, last communication time, and the vehicle it is assigned to (if any). There are functions that lets you request: * The latest communication of this device. * The status of the SIM card in this device. Clicking on these buttons will query for the respective information and display it next to the buttons. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/iot_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=9c640f44956a459abf0388d479853c91) Navigating to the "AssignDevice" tab allows you to assign the IoT device to a vehicle. You can search for vehicles by their VIN, registration number, or internal name. Click on "Connect" to assign the device to the selected vehicle. A popup will ask you to confirm the assignment. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/iot_device_assign.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=699ab755a019a521f1fd3ac90041298b) ## Error Management This section lets you manage **error definitions** that are used to interpret error codes received from vehicles. Error definitions include information about the error's severity, description, and suggested actions. Irrespective of whether errors are received via IoT devices, Bluetooth connectivity, or API integrations, the c.technology system will try to resolve them using the definitions you provide here. You can add individual error definitions by clicking the "Add error definition" button, or import multiple definitions at once using the "Import from CSV" button. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/error_definitions.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=e2fc27851208181c1f78fcc6f1ccd980) A single error definition consists of the following information: * **Device information**: Revision, category, device ID, and vehicle part * **Error identification**: Error code, user-friendly code, severity level * **Severity levels**: Invisible, info, warning, error, critical * **Notification priority**: Low, high, alert * **Multilingual documentation**: Error title, description, troubleshooting steps, and optional documentation URL ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/error_definition_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=cb7a5ed40ad4ae31232370409fd12ba8) ## Firmware Management Firmware updates are a crucial part of modern vehicle maintenance, allowing you to deploy new features, improvements, and bug fixes remotely. The firmware management section provides an overview of all firmware versions that you have uploaded to the platform, along with their deployment status and download counts. > [!NOTE] > > The c.technology cloud platform allows managing firmware updates, but cannot install firmwares on your vehicles. You will need to implement the actual installation process in your IoT device. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/firmwares.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=a92aae78f2707e28050bcc827ea60251) For each firmware update, you have to specify: * **Version metadata**: Version number, assigned vehicle part * **File upload**: Upload the firmware binary file (e.g., .bin, .hex) * **Name and description**: Brief summary of the firmware update, and description of changes ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/engineering/firmware_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=186923b48a03eebbb9a4b1b8600d1e6c) Deploying the firmware update to vehicles will track all installations, including timestamps. This information is shown at the bottom of the firmware details view. # Insights Source: https://docs.ctechnology.io/handbook/oem/insights Basic overview of how your vehicles are used. The Insights section provides a basic overview of how your vehicles are used, including usage patterns, fleet performance, and customer behavior. > [!NOTE] > > This section is currently in beta and will be expanded with more features in future releases. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/insights.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=cd3fdcc584b1751e936281c7c0fd6a69) The initial dashboard shows key metrics such as total distance driven (in the current period), average duration per trip, number of trips, and alerts and notifications generated. Below, a graph of the individual performance on each day of the selected period is shown. # OEM Suite introduction Source: https://docs.ctechnology.io/handbook/oem/introduction Getting started with the c.technology platform as an OEM. The c.technology OEM Suite provides web-based tools to manage vehicle fleets, coordinate with partners, and oversee customer relationships. ![OEM dashboard showing vehicle fleet overview with key performance indicators and navigation menu](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/dashboard.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=a216dd761e986f6768ac0736758efab0) The dashboard shown upon login highlights key performance indicators such as the total usage of vehicles, what's currently important (e.g., maintenance, battery problems), and the current status of your fleet. On the left side, you see the main navigation menu that allows you to access all sections of the OEM Suite. Click the icon if the menu is hidden. ## Sections of the OEM Suite The OEM Suite is divided into the following sections: > **[Vehicle management](/handbook/oem/vehicle)** > > Manage vehicles, type taxonomy, documentation and checklists. > **[Ecosystem](/handbook/oem/ecosystem)** > > Partner overview and vehicle assignment, and customer overviews. > **[Channels](/handbook/oem/channels)** > > News articles, push messages, and support interactions. > **[Insights](/handbook/oem/insights)** > > Analysis of vehicle usage. > **[Engineering](/handbook/oem/engineering)** > > Maintenance management, error definitions, firmware updates, and IoT devices. > **[Organization settings and users](/handbook/oem/settings)** > > How to structure teams and organization settings. # Maintenance Source: https://docs.ctechnology.io/handbook/oem/maintenance Maintenance schedule and rule management. Maintenance focuses around individual maintenance schedules that consist of multiple rules. These schedules can be assigned to vehicle types from your [vehicle taxonomy](/handbook/oem/vehicle-taxonomy), and will then automatically apply to all vehicles of that type. ## Maintenance schedules The main maintenance screen shows all maintenance schedules with their associated vehicle types and rule counts. A schedule can have multiple rules that define when maintenance should be performed. Rules are either **distance-based** (e.g., every 10,000 km), **time-based** (e.g., every 12 months), or based on **operational hours** (e.g., every 500 engine hours). When multiple rules are present, the closest "next due" rule will determine when maintenance is required. Use **Add plan** to create new maintenance plans. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/maintenance/maintenance_plans.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=6fd6d1a90c4716a74d733ba1b8763290) Detailed information about a maintenance schedule is shown in its details view. This information includes a name (potentially translated into multiple languages), and a description. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/maintenance/maintenance_schedules.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=86ff793c86b242f4ef0e388f690c12d6) ## Maintenance rules Each maintenance schedule can have multiple rules that define when maintenance should be performed. The rules are presented as a long list including their name, description, and trigger conditions. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/maintenance/maintenance_schedule_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=11eec8d6f2c6fcd14995f90f15edd825) The following rule types are available: * **Distance-based**: Trigger maintenance after specific odometer readings * **Time-based**: Schedule maintenance at calendar intervals (weekly, monthly, annual) * **Operational hours**: Trigger based on engine runtime hours When multiple rules are defined, the closest upcoming maintenance event will be based on the vehicle's current data. Clicking on the edit icon next to an (enabled) trigger condition opens the rule details view, where you can modify the rule's settings. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/maintenance/maintenance_rule_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=53c1219646a7ce728e4992e729417e3f) You can define: * An **initial offset** to delay the first maintenance event (e.g., first service after 1,000 km or 3 months) * A **recurrence interval** to set how often maintenance should be performed (e.g., every 10,000 km or every 12 months) * A **tolerance** to allow early maintenance (e.g., 500 km or 1 month before the due date) ## Maintenance schedule sharing Maintenance schedules can be shared with vehicles via your [vehicle taxonomy](/handbook/oem/vehicle-taxonomy). Simply select the vehicle types you want to assign the schedule to, and save your changes. ## Maintenance partners You can assign maintenance schedules to your service partners, allowing them to view and manage maintenance for vehicles assigned to them. > [!NOTE] > > This functionality is currently only available for selected partners and will be available publicly in future releases. # Notifications Source: https://docs.ctechnology.io/handbook/oem/notifications Notify your team when something happens to a selection of your vehicles, by web, app and email. The **Notifications** section is shared between the OEM Suite and the other organization types, such as distributors, dealers, service partners, rentals and fleet operators. As OEM organizations see the same section, please refer to the [Notifications documentation for organizations](/handbook/professional/notifications) for the full description of triggers, vehicle selection, recipients, channels and settings. In short, you define a named rule once for a selection of your vehicles, choose up to 25 team members and decide per person whether they are notified by web, app or email. Every notification is always kept in the recipient's notification history. > [!NOTE] > > Notification rules of your organization are separate from the personal notification rules that every user can set up for a single vehicle. See [Notifications and alerts](/handbook/private/notifications) for those. # Organization settings Source: https://docs.ctechnology.io/handbook/oem/settings Managing your organization settings, support info, and visual customization. In the settings section, you can manage various aspects of your organization, including general organization settings, support information, and visual customization options. You can access these settings by clicking on the settings menu entry in the sidebar. ## Organization settings The basic organization settings allow you to update your organization's name, address, and contact information. This information may be shown to your customers in various places, such as the Private App or in email communications. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/settings_organization.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=9fd8bd1c4388786b4acfefe20db46da5) The organization identifier is a "reverse domain" notation id that uniquely identifies your organization within the system. It is set when your organization is created and cannot be changed later. > [!NOTE] > > In any communication with the support team, please always include your organization identifier to help us assist you more efficiently. ## Support settings For support, you can specify a support email address and phone number that your customers can use to reach out to you for assistance. Additionally, you can specify if you should be sent emails upon new support messages from your customers. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/settings_support.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=e4cec71864b27651e29ca49f6ea68314) ## Visual settings The visual settings allow you to customize the appearance of the OEM Suite, Professional Hub and Private Webapp for your organization. It allows uploading various logos and images that will be shown to your customers in different places. You can also customize the primary color used in the apps to match your corporate design. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/settings_visual.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=f45e8b26ed33b63dfa93204066c6c3e2) > [!NOTE] > > White-labeling is only available for enterprise customers. Please contact your account manager for more information. # Team management Source: https://docs.ctechnology.io/handbook/oem/team Managing your organization members and their roles. The team management screen allows you to manage your organization members, assign roles, and control access permissions within your organization. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/team.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=789ac7d51f0556a9bc8abcf8a378dab7) The system supports several organizational roles with different access levels: * **Administrator** `USER_ORG_ADMIN` Full administrative access to all organization functions. * **Standard User** `USER_ORG_STANDARD` Standard user access for routine operations. Can not manage team members. * **Service User** `USER_ORG_SERVICE` Service-focused access for maintenance and support. * **Marketing User** `USER_ORG_MARKETING` Marketing access for customer insights and analytics. * **Engineering User** `USER_ORG_ENGINEER` Engineering access for technical data and development. Each role determines what sections of the dashboard and what actions the team member can perform. To add a new team member, click the "Add organization member" button. If the user already has an account in the system, it will be linked to your organization. If the user does not have an account yet, an invitation email will be sent to them to create one. # Vehicle management Source: https://docs.ctechnology.io/handbook/oem/vehicle How to manage vehicles through the OEM dashboard. The Vehicle Management section provides comprehensive tools for managing individual vehicles, creating vehicle taxonomies, and organizing documentation and checklists. For additional details, see: * [Vehicle taxonomy](/handbook/oem/vehicle-taxonomy) for defining taxonomies * [Documents and checklists](/handbook/oem/documents) for managing documentation ## Vehicle overview The main vehicle screen displays all vehicles in a searchable table with vehicle name, category, VIN/serial number, status, and IoT device status. ![](https://mintcdn.com/ctechnologyag/2fKpZfAzamlnzOS6/images/handbook/oem/vehicle/vehicles_table.png?fit=max\&auto=format\&n=2fKpZfAzamlnzOS6\&q=85\&s=c370223416c550982ccd08617b250900) **Adding vehicles:** * **Add existing vehicle** (via "add vehicle" dialog): Register existing vehicles by entering their short ID. Use this if you purchased IoT devices from [c.technology AG](https://shop.ctechnology.io) or otherwise need access to known vehicles. * **Create new vehicle** (via "add vehicle" dialog): Set up completely new vehicles (initially without IoT devices, they can be added later). * **Import from CSV**: Bulk import multiple vehicles. You can either add IoT devices during import or link them later. Click any vehicle to access detailed management across four tabs: Vehicle details, IoT & parts, Support & maintenance, and Subscriptions. ## Vehicle details On this tab, you can manage basic vehicle information and organizational assignment. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/single_vehicle_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=56ea11f0cacec3f797ca26e664590227) You cannot edit any of the identification information shown on top, as this is managed by c.technology. The organization-specific fields are fully under your control and can be used to link a vehicle to other systems, or a type from the [vehicle taxonomy](/handbook/oem/vehicle-taxonomy). The last box contains all fields that are shared with *everyone* who has access to the vehicle: its name, license plate, VIN, etc. \[!WARNING] If you select a *vehicle type* from your taxonomy, the vehicle will automatically inherit all fields defined for that type, and the fields *brand* and *type* from the last section will not be used. ## Vehicle data The data tab provides detailed insights into the vehicle's data and status. \[!NOTE] All data access will always be in accordance with organizational or personal access rights. For example, except if your organization is a `VEHICLE_OWNER` of a vehicle, its GPS location will never be shown. For each numerical display, clicking on it will open a detailed time series chart with time extent selection. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/single_vehicle_data.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=b01891cfc583ff92f82c9941908c0cb7) If access is available, individual trips can be explored to get an overview of the vehicle usage. Finally, a yearly overview of the vehicle usage is given. Use the selectors on the top right to change the year. ## IoT & parts This tab allows you to manage IoT devices / Bluetooth connectivity and track installed vehicle parts. An IoT device is optional if a) you solely upload data via APIs or b) the vehicle is solely accessed via Bluetooth. If an IoT device is connected, you can see its status and details on the top. If no device is connected, you can add one by clicking the "Add IoT device" button. You can also remove an existing device if needed, for example, if you replace it or move it to another vehicle. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/single_vehicle_iot_parts.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=552bc5d178010f309904f48383ae116b) The buttons next to the individual boxes let you query the platform for the latest data from the vehicle, or its SIM status. The result of the query will be shown in the boxes next to the buttons. [Vehicle parts](/handbook/oem/vehicle-taxonomy#vehicle-parts) are used to track all installed components of a vehicle, whether factory-installed or aftermarket. This is helpful for storing serial numbers, managing warranties, etc. \[!NOTE] Vehicle parts are also used for firmware management. You can assign firmware versions to parts, and then install them via the API. All installations are tracked in the installation history. Vehicle parts can be automatically detected and synchronized if the IoT device or Bluetooth connectivity supports this feature. ## Maintenance The maintenance tab provides a summary of all past maintenance that has been performed on the vehicle. Additionally, all (DTC or other) errors that have been detected on the vehicle are shown. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/single_vehicle_maintenance.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=8a7d2298d9e5ce2aea2398a2dbf921b8) If you added error definitions in the [engineering section](/handbook/oem/engineering), additional information will be shown for each error, including its severity, description, and suggested actions. ## Support In the support tab, you can manage access control and support tickets for the vehicle. As an OEM, you have the possibility to change user access for level 3 support. \[!WARNING] Note that all changes to user and organizational accesses are logged and auditable. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/single_vehicle_support.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=b1432a1afe1c6cf7400116e08564838f) The support section shows all tickets that have been created for the vehicle, including their status and history. Clicking on a ticket opens its details, see [support ticket management](/handbook/oem/channels#support). ## Subscriptions The subscriptions tab provides an overview of all active and past service subscriptions associated with the vehicle. \[!NOTE] For most of your vehicles, you will not have to manage individual subscriptions, as they are handled globally on an organization level. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/single_vehicle_subscriptions.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=8451a9c204a06f0d5c44e06d684a8eef) # Vehicle taxonomy Source: https://docs.ctechnology.io/handbook/oem/vehicle-taxonomy Managing vehicle categories, families, and types. The Vehicle Taxonomy section organizes your product lineup into a hierarchical structure that supports document management, maintenance scheduling, and parts compatibility. ## Taxonomy structure The platform uses a three-level hierarchy: **Categories** → **Families** → **Types**. Each vehicle can be assigned one type per organization, which automatically links it to the corresponding family and category. **Parts** are orthogonal, and can be associated with individual vehicles. * **Categories**: High-level groupings (e.g., "Adventure," "Cruiser," "Marine") * **Families**: Product lines sharing design characteristics (e.g., "Tenere series," "Sportster line") * **Types**: Specific models (e.g., "Tenere 700," "Sportster 883") * **Parts**: Components and hardware installed on vehicles ## Vehicle categories This tab lets you manage the highest level of vehicle organization with broad product categories. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/vehicle_categories.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=5db18d6a8bc84b5af8c90205fa2ef545) Add new categories with the **add category** button. Each category needs at least a name, optionally a description can be added. \[!NOTE] The system prevents deletion of categories that still have families assigned to them. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/vehicle_category_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=7ddc1c9124431207f93d6554ec797156) Categories serve as the foundation for organizing your entire product portfolio and can be used to share documents, maintenance schedules, etc. with the respective vehicles. ## Vehicle families Similarly, this tab lets you organize related vehicle types that share common characteristics within each category. ![](https://mintcdn.com/ctechnologyag/bQ518Ckb6IU5Uqj2/images/handbook/oem/vehicle/vehicle_families.png?fit=max\&auto=format\&n=bQ518Ckb6IU5Uqj2\&q=85\&s=4da68b68b7b7a22d972c8ce749eb2f9f) **Family management:** * Create families using **add family** button * Select parent category and define family characteristics * Group models with shared design, features, or market positioning * Delete unused families (system prevents deletion if types exist) Families enable bulk management of related products and streamline maintenance scheduling across similar vehicles. ## Vehicle types On the lowest level, this tab lets you define specific vehicle models that customers purchase and register in your system. ![](https://mintcdn.com/ctechnologyag/2fKpZfAzamlnzOS6/images/handbook/oem/vehicle/vehicle_types.png?fit=max\&auto=format\&n=2fKpZfAzamlnzOS6\&q=85\&s=7bdd6823b6c3dd8735be0ab87e001bf0) **Type management:** * Create specific models using **add type** button * Associate with parent family and define detailed specifications * Configure model-specific features and capabilities * Delete unused types (system prevents deletion if vehicles exist) ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/vehicle_type_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=24e1bd350a74a30f684d791bde6e7e0e) Vehicle types represent the actual products in your catalog and serve as the basis for vehicle registration, maintenance scheduling, and parts compatibility. Vehicle type may also be associated with additional properties such as fuel type, maximum speed, or weight class. These properties may be used to custom-tailor UI elements in the mobile app(s). ## Vehicle parts Vehicle parts can be assigned to vehicles to represent installed components, hardware, or accessories. They are independent of the vehicle taxonomy and can be used to track both factory-installed and aftermarket parts. Vehicle parts are particularly useful for: * Managing component inventories * Keeping track of serial numbers and warranties * Associating firmware updates with specific hardware ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/vehicle_parts.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=43520c7b0eea8e4f31784b18989c60d8) The detail view lets you additionaly declare if a vehicle part is updateable (firmwares may then be associated with it) and add a part image that may be shown in the mobile app to vehicle owners. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/vehicle/vehicle_part_details.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=bb0e0cd1d3e60748c19113ac023b21be) If you enable firmware updates for a vehicle part, the last box will appear, allowing you to manage firmware versions associated with this part. You can add new firmware versions, and set existing ones as active / inactive to control deployments. \[!NOTE] By default, the latest active firmware version will be offered to vehicles with this part installed (following semantic versioning). \[!NOTE] By defining "development" parts and assigning them to test vehicles, you can test firmware updates before rolling them out to production vehicles. # Bluetooth Source: https://docs.ctechnology.io/handbook/private/bluetooth How to connect your vehicle's Bluetooth device to the Private App for real-time data transmission. When selecting a Bluetooth vehicle, you will see the "Connect Bluetooth" button on the dashboard, directly above the vehicle overview. Tapping this button will open the Bluetooth connection screen, where you can see available devices and their signal strength. By default, it will filter only compatible devices. You can press "Show all devices" to see all available Bluetooth devices in your vicinity. ![Mobile app showing Bluetooth connection interface for device pairing](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/dashboard-2.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=94ff73d8a5163232614804f6cd024b49) Connecting to a supported device will show the connection screen where you should follow the instructions to complete the pairing process. Upon successful connection, you will be taken back to the dashboard where you can see the connection status in green. If Bluetooth connection is lost, the app will automatically try to reconnect when you are back in range of the vehicle. Similarly, the app will also try to reconnect to known devices when you open the app. ## Troubleshooting If you are having trouble connecting to your vehicle's Bluetooth device, try the following steps: 1. Ensure that your vehicle's Bluetooth device is powered on and within range of your smartphone. 2. Make sure that Bluetooth is enabled on your smartphone. 3. Restart the Private App and try connecting again. 4. If you still cannot connect, go to your smartphone's Bluetooth settings, forget the vehicle's Bluetooth device, and then try reconnecting through the Private App. 5. Ensure that no other device is currently connected to the vehicle's Bluetooth device, as this may prevent a new connection. 6. If you continue to experience issues, consult your vehicle's manual or contact your vehicle provider for further assistance. # Cockpit Source: https://docs.ctechnology.io/handbook/private/cockpit Real-time vehicle monitoring and navigation interface with live data displays and trip tracking. The cockpit provides a real-time monitoring interface that displays your vehicle's current position, status, and performance data on an interactive map. This feature serves as your primary navigation and monitoring tool during active journeys. You can access the cockpit through the main navigation of the Private App. ![Mobile app showing vehicle cockpit interface with real-time data and controls](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/cockpit.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=bc8a7950335b7e779b26e5320ea6b7a8) ## Overlays and settings The cockpit offers various data overlays that provide real-time information about your vehicle's performance and status. These overlays can be cycled through by tapping on the "switch overlay" button . Similarly, you can use to access cockpit settings, where you can customize display preferences, map options, and trip recording settings. Depending on your app, vehicle type, and subscription, you might have different overlays and map styless available. Click on the gauges to change their units. Globally, units can be changed in the [profile settings](/handbook/private/settings#profile-settings). If your vehicle supports this, a range indicator is shown as a circle around your current position. \[!WARNING] Range estimation depends on many factors such as local conditions, weather, terrain, and your driving style. Use it as a general guide rather than a precise prediction. For marine applications, additional safety features such as shore zones and shallow water warnings may be available depending on your location and vehicle configuration. \[!WARNING] Safety features depend on your vehicle type and configuration, and may not always be correct. Always prioritize safe navigation practices and local regulations. ## Trip recording As soon as you embark on a journey with your vehicle, the cockpit automatically starts recording your trip. An additional box with information about your current trip appears at the bottom of the screen. This box shows the elapsed time, distance traveled, and average speed for your current trip. The trip itself is shown as a line on the map, allowing you to visualize your route in real-time. When you make a short stop, previous recordings are shown as a faded line, while the current leg of your trip is highlighted. When you make a long stop, the current trip is automatically ended, and a new trip will be started when you resume your journey. You can find completed trips in the [logbook](/handbook/private/logbook). ## Issue indicators If any issues arise, you will see indicators on the top right of the screen. These indicators provide information about the connection status of your IoT device, server connectivity, and Bluetooth status (if applicable). If you feel the interface is updating slowly, try to lower the update frequency in the [cockpit settings](/handbook/private/bluetooth#connection-and-troubleshooting). ## Points of interest The cockpit provides access to various points of interest (POIs) relevant to your journey. These vary based on your vehicle type and configuration, but always include POIs you record yourself (via "Drop POI" in the dashboard). # Dashboard Source: https://docs.ctechnology.io/handbook/private/dashboard Overview of key vehicle metrics, current status, and recent activities upon logging into the Private App. The dashboard shown upon login highlights key vehicle metrics such as current location, engine status, battery level, and recent activities. In addition, it shows tiles with important information (e.g., news articles or errors) and additional apps (if available). Such apps may include custom interaction apps provided by your vehicle manufacturer or dealer, e.g., a booking app for rental vehicles or a hibernation service for long-term seasonal storage. ![Mobile app showing vehicle dashboard with location, status, and quick action buttons](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/dashboard-2.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=94ff73d8a5163232614804f6cd024b49) Clicking on the vehicle card next to the map at the top of the screen takes you to the vehicle status screen, which provides detailed information about all the parameters your vehicle is reporting. ## Vehicle status details The vehicle status screen shows the most important four parameters at the top of the screen. Below that, you can see additional parameters grouped by categories such as "Engine", "Battery", "Fuel", "Connectivity", etc. ![Mobile app showing detailed vehicle status screen with parameters and categories](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/status.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=f569e7a80ec7a06b52c4e81e06be731d) For certain parameters, you can click on the info icon ⓘ to get additional information about what the parameter means and how it is measured. ## Quick actions Below the information header, you find a row of quick action buttons that allow you to perform common tasks related to your vehicle. By default, the following quick actions are available: * **Drop POI**: Save your current location as a point of interest (POI) for easy navigation later. * **Screen on**: Keep your device screen on while using the app to prevent it from dimming or locking. * **Share vehicle**: Share access to your vehicle with another user by entering their email address. Optionally, functions such as *unlock*, *flash\_light*, *turn\_on*, etc. may be available depending on your vehicle type and configuration. ## Vehicle apps Finally, you find a selection of larger tiles at the bottom of the screen that provide access to additional apps or features related to your vehicle. These apps may vary based on your vehicle manufacturer or dealer and can include functionalities such as: * **News articles**: View the latest news and updates related to your vehicle or manufacturer. * **Error messages**: Check for any error codes or warnings reported by your vehicle. * **Maintenance reminders**: Get notifications about upcoming maintenance tasks or service appointments. * **Statistics**: Access detailed statistics about your vehicle's usage, performance, and efficiency. * **Custom apps**: For custom apps, see [vehicle apps](/handbook/private/vehicle-apps). # Private App introduction Source: https://docs.ctechnology.io/handbook/private/introduction Getting started as a private vehicle owner using c.technology mobile apps and web interface. Individual vehicle owners access the c.technology platform through mobile applications (clickahoy, clickrider, and white-labeled versions) and a web interface to monitor, manage, and maintain their vehicles. ![Mobile app showing vehicle dashboard with key metrics and navigation](https://mintcdn.com/ctechnologyag/2fKpZfAzamlnzOS6/images/handbook/private/dashboard.png?fit=max\&auto=format\&n=2fKpZfAzamlnzOS6\&q=85\&s=cb5067cd362309dcabe1c6f6b41d575a) The dashboard shown upon login highlights key vehicle metrics such as current location, engine status, battery level, and recent activities. The main navigation is on the bottom of the screen, allowing you to access all sections of the Private App. From each section, you can dig deeper into specific features and settings. Next to the Private App, all vehicle owners can use the web interface under [app.ctechnology.io](https://app.ctechnology.io) (or any white-labeled version thereof) for additional features and a desktop-optimized experience. ## Sections of the Private App The Private App is divided into the following sections: > **[Dashboard](/handbook/private/dashboard)** > > Manage vehicles, type taxonomy, documentation and checklists. > **[Cockpit](/handbook/private/cockpit)** > > News articles, push messages, and support interactions. > **[Logbook](/handbook/private/logbook)** > > Analysis of vehicle usage. > **[Vehicle apps](/handbook/private/vehicle-apps)** > > Partner overview and vehicle assignment, and customer overviews. > **[Settings](/handbook/private/settings)** > > Maintenance management, error definitions, firmware updates, and IoT devices. For some of the OEM-specific Private Apps, you can find additional information in the respective sections: * [Torqeedo TorqView](/handbook/oem-app/torqview) - Additional information specific to the Torqeedo TorqView application. # Logbook Source: https://docs.ctechnology.io/handbook/private/logbook How to use the logbook section to analyze and manage your vehicle trips. The logbook feature provides a comprehensive trip recording and management system that automatically tracks your vehicle journeys and allows you to view, edit, and share trip details. All trips are recorded automatically when your IoT device is connected and active. When you use a Bluetooth connection, trips are recorded as long as the app is open and the screen is on. In the logbook section, you can view a list of all your recorded trips. In the web app under [app.ctechnology.io](https://app.ctechnology.io), you can additionally see *vehicle actions*, such as speed alerts or checklist submissions, in the logbook. ![Mobile app showing logbook with trip history and vehicle journey details](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/logbook.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=b4bd0ff39eefc1099656fa07fcadfceb) By default, each trip is presented on its own card showing key information such as departure time, duration, distance, average speed, maximum speed, and fuel consumption (or battery usage for electric vehicles). Trips with poor GPS signal quality are automatically filtered out to ensure data accuracy. Trips with questionable data quality are marked as such and you will be prompted to either keep or delete them. Clicking on a trip card opens the detailed trip overlay, which provides additional information and lets you edit the trip. ## Trip details On top of the trip details screen, you will find a map image showing the route of your trip. Below that, you can see detailed statistics about your trip, including total duration, distance, fuel consumption, average speed, and maximum speed. Finally, you can see the trip name, driver, and notes. ![Mobile app showing detailed trip view with route map and travel statistics](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/trip.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=f549bb2534613ced46cad35f232a557e) To view the map in full, click on the map image. To edit the trip, click on the edit button (pencil icon). Editing lets you change the trip name, driver, notes, and manually override the fuel consumption. You can always delete a trip by long pressing on the trip card in the trip list. ## Trip sharing Depending on your vehicle and its manufacturer, you may be able to share trips with other users. Click on the switch to make the trip public. You may also be able to download a picture of the trip or share a link to the trip. ## Trip Recording Requirements For optimal trip recording performance, ensure: * your IoT device remains connected (if you have an IoT device installed) * and your smartphone app stays active during journeys (if you use Bluetooth). Extended periods with the app minimized or screen off may result in gaps in trip recording data. ## Troubleshooting * **Trips not recording**: Verify your IoT device connection and ensure the app has necessary location permissions enabled. * **Missing trip data**: Check your internet connection and try refreshing the logbook by pulling down on the trip list. * **Cannot load trip**: This message indicates either a network connectivity issue or insufficient permissions to access the trip data. Verify your internet connection and account permissions. # Login and onboarding Source: https://docs.ctechnology.io/handbook/private/login-onboarding How to create an account, log in, and get started with the Private App. Upon first launching any of the Private Apps (clickahoy, clickrider, or white-labeled versions), you will be presented with the login screen. ![Mobile app showing login screen with email and password fields](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/login.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=676b161229277d7e974a5c1760042af0) If you do not have an account, tap "Create account" to start the registration process. You will need to provide a valid email address and create a secure password. After submitting your information, you will receive a confirmation email to verify your account. ![Mobile app showing account creation form with registration fields](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/create-account.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=c9b3ceecbbf6937501189db41569ede8) Once your account is verified, you can log in using your email and password. ## Onboarding After logging in for the first time, you will be guided through an onboarding process to set up your profile and link your vehicle(s) to the app. This onboarding process may be customized based on the specific Private App version you are using (clickahoy, clickrider, or white-labeled). Generally, you will be prompted for the following information: * **Personal details**: First and last name (simply to make the app use more personal). * **Vehicle short id**: You will have received this id from your vehicle provider (e.g. dealer, rental company, etc.) or it is printed on a sticker on your vehicle. * **Acceptance** of terms and conditions and privacy policy. Upon successful onboarding, you will be taken to the main dashboard of the Private App, where you can start managing and monitoring your vehicle(s). > [!NOTE] > > If someone already has access to the vehicle which you want to add during onboarding, they will get an email to approve your request. This is a security measure to prevent unauthorized access to vehicles. # Maintenance Source: https://docs.ctechnology.io/handbook/private/maintenance How to view the current maintenance status, track upcoming maintenance, and access professional service providers and official documentation. The maintenance section of the Private App provides a comprehensive overview of your vehicle's maintenance status (past official and unofficial maintenance works), upcoming service requirements, maintenance history, and access to professional service providers and official documentation. This feature helps you stay on top of your vehicle's maintenance needs and ensures it remains in optimal condition. The maintenance tile on the dashboard shows a summary of the upcoming maintenance requirements, including the next service due and a progress bar indicating how close you are to that service. ![Mobile app showing maintenance tile on dashboard with upcoming service requirements](https://mintcdn.com/ctechnologyag/qX9VhUX1pj8K__2P/images/handbook/private/maintenance-dashboard.png?fit=max\&auto=format\&n=qX9VhUX1pj8K__2P\&q=85\&s=96bd3eb13221667e5622db6dbd0ae0eb) Clicking on the tile takes you to the maintenance section of the app. ## Past and upcoming maintenance On top of the maintenance screen, you can see a summary of when the next maintenance is due. Depending on your vehicle, this may be based on: * time, e.g., every 12 months, * mileage, e.g., every 15,000 km, or * motor running time, e.g., every 500 hours. If multiple criteria apply, the most urgent one is shown. On the bottom of the maintenance screen, you can see a history of past maintenance works, including the date, mileage, and description of each service. ![Mobile app showing maintenance history and upcoming service schedule](https://mintcdn.com/ctechnologyag/qX9VhUX1pj8K__2P/images/handbook/private/maintenance-details.png?fit=max\&auto=format\&n=qX9VhUX1pj8K__2P\&q=85\&s=e0b5fe419de55b0c0cf8d057517b216e) Clicking on the summary takes you to the detailed view of the upcoming maintenance, including manufacturer-specified maintenance tasks, their descriptions, and their due dates or mileages. If your vehicle supports it, you may directly choose a professional service provider to book the maintenance service. ![Mobile app showing detailed upcoming maintenance tasks and service provider selection](https://mintcdn.com/ctechnologyag/qX9VhUX1pj8K__2P/images/handbook/private/maintenance-upcoming-details.png?fit=max\&auto=format\&n=qX9VhUX1pj8K__2P\&q=85\&s=0984bdb1703b861b07003bad38116445) ## Maintenance partner discovery and selection By default, maintenance partners close to your current location are shown. Upon selecting a maintenance partner, you can either open a ticket with them, or - if they offer it - directly book a maintenance appointment. ## Official documentation access The maintenance screen also allows you to directly access the official maintenance documentation provided by your vehicle manufacturer. This is the same as the documentation that is accessible via your [vehicle documents](/handbook/private/notes) section. Ensure that you are looking at vehicle documents, and not your personal ones. # Notes, documents, checklists Source: https://docs.ctechnology.io/handbook/private/notes Comprehensive tools for recording, organizing, and sharing information related to your vehicle. The three sections notes, documents, and checklists are grouped together as they provide complementary functionalities for managing information related to your vehicle. * **Notes** are used for general text-based information and messaging among vehicle users and service providers. * **Documents** allow you to store and organize files and images related to your vehicle. They also contain manufacturer-provided documents such as user manuals or warranty information. * **Checklists** help you manage and track maintenance tasks, inspections, and routine procedures for your vehicle. They may be supplied by manufacturers or created by you or your service provider. ## Notes There are two types of notes available: * **General notes**: These are text-based notes that can be created, edited, and organized by you. They are not tied to any specific date and can be used for general information sharing. You can use [Markdown](https://www.markdownguide.org/basic-syntax/) to format your notes. * **Calendar messages**: These are date-specific notes that allow you to record information tied to specific dates. They are useful for logging events, reminders, or observations related to your vehicle on particular days. You can find all notes under the "Notes" section in the app navigation. ![Mobile app showing notes section with general notes and calendar messages](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/notes.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=efb507a6d69d5d166bbbdaa12ccd5d1c) When adding a new note, a dialog will prompt you to enter a name for the note. You can edit and delete notes by swiping left on the note item in the list. When editing calendar messages, you will be presented with a calendar to select the date for the message. Dates that already have messages associated are highlighted with a dot. ## Documents Documents can be: * **Personal**: These documents are associated with your user account and can be accessed regardless of which vehicle you are currently viewing. They are useful for storing general documents such as your driver's license, insurance papers, or other personal files. * **Vehicle-specific**: These documents are tied to a specific vehicle and can include files such as the vehicle's user manual, warranty information, service records, or inspection reports. They may be uploaded by you or provided by your vehicle manufacturer or service provider. > [!NOTE] > > You can edit your own documents, but not documents uploaded by others (e.g., your dealer or service provider). ![Mobile app showing document storage with personal and vehicle-specific files](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/documents.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=0c5ca9ab99846fb8bfb8362fa74250c3) To upload a document, you need to provide a name and select a file from your device. \[!NOTE] Uploading documents will prompt you for permission to access (parts of) your device's storage. \[!WARNING] Currently, you can only upload images / photos from the mobile app. PDF documents can only be uploaded through the web dashboard at [app.ctechnology.io](https://app.ctechnology.io). \[!WARNING] Documents uploaded through the mobile app are not associated with a category. If you need to categorize documents, please use the web dashboard at [app.ctechnology.io](https://app.ctechnology.io). You can edit or delete documents by swiping left on the document item in the list. Images can be viewed directly in the app, while PDF documents will open in your device's default PDF viewer. ## Checklists Checklists help you organize and track completion of maintenance tasks, inspections, and routine procedures for your vehicle. Checklists may be created through the web dashboard under [app.ctechnology.io](https://app.ctechnology.io) and will be automatically synchronized to your mobile app. ![Mobile app showing checklist interface with task completion checkboxes](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/checklists.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=51c2f94bea4adbf5263c7ed85e30d276) When filling in a checklist, you can select individual checklist points by tapping their checkboxes. \[!NOTE] You do not need to complete all checklist items. You can select only the items that are relevant or completed. You can also add comments or notes related to the checklist completion using the comment field at the bottom of the checklist. Filling in a checklist will add a permanent record of the checklist execution, including the selected items, completion date, and any comments you provided into the vehicle's logbook. \[!WARNING] Currently, filled in checklists can only be viewed in the web dashboard at [app.ctechnology.io](https://app.ctechnology.io). They are not visible in the mobile app. # Notifications and alerts Source: https://docs.ctechnology.io/handbook/private/notifications Comprehensive guide to managing notification settings and viewing alerts for vehicle events, maintenance reminders, and system updates. The notification system keeps you informed about important vehicle events, maintenance requirements, and system updates. This feature provides customizable alert preferences and a centralized notification management interface. \[!WARNING] In the Private App, only a streamlined version of the notification settings is available. For full control over notification rules, please use the web interface at [app.ctechnology.io](https://app.ctechnology.io) or any white-labeled version thereof. ![Mobile app showing notification settings with custom rules and preferences](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-notifications.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=0d90adbd95c3eeea1e8e8626409b8f37) ## Configuring custom notification rules In the web application under [app.ctechnology.io](https://app.ctechnology.io), navigate to the settings of a vehicle through the respective menu entry. ![Web application showing notification rules configuration interface with property selection and thresholds](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-notifications-webapp.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=dea1323d1cdad08053087a514708d79a) Select the property you want to configure notifications for (e.g. "Battery level"), an operator (e.g. "less than"), and a threshold value (e.g. "20%"). Choose a priority, as explained below (`LOW`, `MEDIUM`, `HIGH`, `ALERT`), and click "Add rule". You can delete existing rules by clicking the trash can icon next to the rule. ## Receiving alerts As explained in the previous section, alerts can be received as any of: * **Push notifications** (`ALERT`): Delivered directly to your mobile device when the app is installed and notifications are enabled. * **Desktop popup** (`HIGH`): Displayed on any desktop computer where you are logged into the web application. * **Webapp popup** (`MEDIUM`): Shown as in-app notifications within the web application. * **Logbook entry** (`LOW`): Recorded in the logbook section of the web application for later review. Clicking on a push notification will take you directly to the relevant app. Both in mobile apps as well as in the web application, a counter badge on the notification icon indicates the number of unread notifications awaiting your attention. You can open the navigation drawer by clicking on the icon to view all notifications. Clicking "Mark all as read" will clear the unread status from all current notifications and remove the notification badges throughout the app. ## Organization notifications If you are a member of an organization, a team member of your organization can set you up as the recipient of an organization notification rule. Organization rules watch a selection of the organization's vehicles and notify the people the organization chose. You do not have to configure anything to receive them. For how organizations create rules, see [Notifications for organizations](/handbook/professional/notifications). ### Receiving organization notifications Every notification from an organization rule is always kept in your notification history. The organization decides whether you are also notified in the web application and by push notification on your mobile device. Notifications from an organization rule show the name of the rule as their title in the notification list . ### Choosing whether you receive emails The organization can also send you emails for a rule. You decide whether you want them. Open your profile settings and go to **Organization notifications**. The pane lists every rule that notifies you, with the channels the organization enabled for you (History, Web and App) and an email switch for each rule. * Switch the email off to stop the emails of that rule. The switch is unavailable with the note "The organization sends no emails for this rule" if the organization did not enable emails for you. * After you switched emails off, the pane shows when you unsubscribed. Switch the email on again at any time. * Only you can switch emails back on. The organization cannot override your choice. Switching the emails off does not change your notifications in the app or your notification history. ### Unsubscribing from an email Every email from an organization rule contains an unsubscribe link for each rule it reports on. Open the link to see the rules and the organization it concerns, and click **Unsubscribe**. You do not need to log in. Many email programs also show their own unsubscribe button, which works in one click. After unsubscribing, the page confirms "You are unsubscribed". To change your mind, click **Subscribe again** on the same page, or switch the emails on in your profile settings as described above. If the link shows "This link is not valid", it is incomplete or the rule no longer exists. Once you are logged in, you can manage your organization notifications in your profile settings. # Settings Source: https://docs.ctechnology.io/handbook/private/settings Managing vehicle settings, maintenance, and IoT device configurations in the Private App. The settings section allows you to manage various aspects of your vehicle and app experience. This includes: * **User settings**: Update your personal information, change your password, and manage account security. * **User access**: Invite other users to access your vehicle, manage their permissions, or remove their access. * **Vehicle settings**: View and edit vehicle details, manage vehicle-specific settings, and access vehicle documentation. * **Vehicle parts**: Check for firmware updates for your vehicle's components, view error codes, and manage connected IoT devices. ## Settings overview The most right icon in the bottom navigation bar opens the settings section. Next to common tasks (see other sections of this handbook), you can manage user and vehicle settings. ![Mobile app showing main settings screen with personal and vehicle options](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=2561b1d8498df301b437ad205afdf48c) Under "personal", you can find all user-related settings, while "vehicle, engine & services" contains all vehicle-specific settings. ## User settings In this section, you can manage your personal information, change your password, and configure account security settings. \[!NOTE] You cannot change your email address directly. If you need to update your email, please contact support. ![Mobile app showing user settings with personal information and account options](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-user.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=4ea31cf4cd583394af02fa0aa5b014e0) Navigating to "account settings" lets you reset your password, and request a deletion of your account. \[!NOTE] You can also request an excerpt of your personal data in compliance with data protection regulations from this section. Under "personal notifications", you can configure which notifications you want to receive (e.g., product updates, newsletters, etc.). ### User access The user access section allows you to manage who has access to your vehicle. To reach it, navigate to "user access" under the "vehicle settings" section. ![Mobile app showing user access management with invitation and permission settings](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-user-access.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=04c55e955e16c17dc6d947b63343ac8e) You can invite new users by entering their email address and selecting the appropriate permission level (e.g., view-only, full access, etc.): * **Owner**: Full access to all vehicle features and settings, including inviting/removing users. Cannot be removed by other users. * **Vehicle user**: Full access to all vehicle features and settings, except inviting/removing users. * **Read-only**: View vehicle status and information but cannot perform any actions or changes. * **No details and no editing**: Limited access to view only basic vehicle information without any editing capabilities. * **Only current status**: View only the current status of the vehicle without access to historical data or settings. > [!WARNING] > > Note that all modifications of user accesses are immutably logged in the vehicle's logbook for auditing purposes. ## Vehicle settings The vehicle settings section allows you to view and edit vehicle details such as its name or image (used throughout the app). ![Mobile app showing vehicle settings with device assignment and configuration options](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-vehicle.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=e04961e0f691f1f073d14a296cb1396f) > [!NOTE] > > If you outfitted your vehicle with an IoT device yourself, you can also assign a brand and type to the device here. ### Engine and IoT device settings Going deeper, the engine settings section provides information about your vehicle's engine, such as its fuel type, tank capacity, and other relevant details. ![Mobile app showing vehicle engine settings with configuration and monitoring options](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-vehicle-engine.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=13b7f102e2eb05ac92acceaa58765b8b) Under "IoT device", you can view information about the connected IoT device, such as its model, firmware version, and connection status. In addition, you can configure the power source here, such as a 12V car battery or a 24V high-performance battery pack. ![Mobile app showing IoT device information with model, firmware version, and connection status](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/settings-vehicle-iot.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=69a769a6e87ef8a22b756eae9aff310e) # Subscriptions and payments Source: https://docs.ctechnology.io/handbook/private/subscriptions How you can handle subscriptions, payment methods, and billing information for premium services. The c.technology ecosystem requires a **subscription per vehicle**. Often, this subscription is provided by your vehicle manufacturer or dealer as part of your vehicle purchase or lease agreement for a limited time (e.g., 1 year). If you have no active subscription, you will be prompted on the dashboard (both mobile and web app) to activate a subscription. ![Mobile app showing subscriptions screen with service plans and billing options](https://mintcdn.com/ctechnologyag/qX9VhUX1pj8K__2P/images/handbook/private/subscriptions.png?fit=max\&auto=format\&n=qX9VhUX1pj8K__2P\&q=85\&s=1e20c16c71b599a6c5646ed48dc84f36) In addition, some **premium services** may require an additional subscription, e.g., for advanced navigation features or connected car services. These subscriptions can be managed in the "Subscriptions" section of the app. Finally, professional partners may charge **individual fees** for services such as vehicle hibernation, preparation, etc. These fees are handled by the individual "vehicle services" but their invoices may be viewed in the "Subscriptions" section of the app. > [!WARNING] > > Currently, you can see your current subscriptions and payment methods in the mobile app, but you need to manage them in the web application under [app.ctechnology.io](https://app.ctechnology.io). ## Billing methods c.technology only supports credit card payments via Stripe for private and professional customers, and vouchers (can be purchased from the [c.technology shop](https://shop.ctechnology.io)) for private customers. You can add, remove, and update your credit card information in the "Subscriptions" section of your personal settings on the web application. ![Web application showing subscription billing information with credit card management](https://mintcdn.com/ctechnologyag/qX9VhUX1pj8K__2P/images/handbook/private/subscriptions-web-billing-info.png?fit=max\&auto=format\&n=qX9VhUX1pj8K__2P\&q=85\&s=5de1d8bb77bb6e31efb9e8f915b0f83c) Click on *update credit card* to add a new credit card or update your existing one. Click on *terminate subscription* to cancel your current subscription at the end of the current billing period. Click on *manage subscription* to get to the detailed subscription history for the selected vehicle. ## Vehicle subscriptions The "Vehicle subscriptions" section in the vehicle settings on the web application shows the currently active and potential past subscriptions for the selected vehicle. You can see the start and end date of each subscription period, how you have purchased it, and if it automatically renews. If you have not activated a trial subscription, you can activate it from this screen as well. ![Web application showing vehicle subscription details with voucher redemption options](https://mintcdn.com/ctechnologyag/qX9VhUX1pj8K__2P/images/handbook/private/subscriptions-web-vehicle-info.png?fit=max\&auto=format\&n=qX9VhUX1pj8K__2P\&q=85\&s=b515a7afbecdf48fc31cec43c9b2e022) If you have purchased a voucher from the [c.technology shop](https://shop.ctechnology.io), you can redeem it by entering your voucher code in the "Redeem voucher" section at the bottom of the screen. Clicking on *redeem voucher* will apply the voucher to your current vehicle and activate a subscription for the duration specified in the voucher. # Vehicle apps Source: https://docs.ctechnology.io/handbook/private/vehicle-apps Additional vehicle applications and integrations available for private vehicle owners. The vehicle apps section provides access to additional applications and integrations related to your vehicle. These apps may vary based on your vehicle manufacturer or dealer and can include functionalities such as: * **Service booking**: Schedule maintenance appointments or service visits directly through the app. * **Rental management**: For rental vehicles, manage bookings, availability, and customer interactions. * **Hibernation services**: For seasonal storage, manage hibernation settings and monitor vehicle status during off-season periods. * **Custom manufacturer apps**: Access specialized apps provided by your vehicle manufacturer for enhanced vehicle management and features. As an example, consider the following "boat launch" service: ![Mobile app showing vehicle apps interface with custom service applications and features](https://mintcdn.com/ctechnologyag/7HpoiAquo0RrCYhP/images/handbook/private/service.png?fit=max\&auto=format\&n=7HpoiAquo0RrCYhP\&q=85\&s=f403046066a28abb37e784b3217150ce) All apps are always available as tiles on the dashboard screen for quick access. In the following, you find the handbook of some of the most common vehicle apps. You may find additional handbooks under the OEM-specific sections of this handbook. ## Launch The vehicle launch service allows you to schedule and manage boat launches directly from the Private App. This service is particularly useful for boat owners who need to coordinate launches with marinas or service providers. ## Preparation The vehicle preparation service enables you to request and manage pre-launch preparations for your boat. This can include tasks such as cleaning, fueling, and safety checks to ensure your boat is ready for use. ## Hibernation The vehicle hibernation service helps you manage the seasonal storage of your boat. You can schedule hibernation periods, monitor the status of your boat during storage, and request maintenance services as needed. ## Shop The shop service provides access to a range of products and accessories related to your vehicle. You can browse and purchase items such as maintenance supplies, safety equipment, and custom accessories directly through the app. ## Rental For rental vehicles, the rental service allows you to manage bookings, availability, and customer interactions. You can view upcoming reservations, approve or decline booking requests, and communicate with renters through the app. ## Item rental The item rental service enables you to rent out accessories or equipment related to your vehicle. This can include items such as trailers, safety gear, or navigation equipment. You can manage rental availability, track item usage, and handle customer interactions through the app. # Clients Source: https://docs.ctechnology.io/handbook/professional/clients How to manage customer relationships and vehicle ownership. The clients section provides tools for managing customer relationships and vehicle ownership. ![OEM dashboard showing customer management interface with vehicle owner contact information](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/owners.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=c56a04b1fdf1f80da6432ce225b8124b) The clients section corresponds to the "Customers" menu item in the OEM Suite. Please refer to the [OEM Suite documentation](/handbook/oem/ecosystem#customer-management) for more details. > [!NOTE] > > In comparison to the OEM Suite, you may have limited access to certain features, depending on your organization's permissions and settings. # Documents and checklists Source: https://docs.ctechnology.io/handbook/professional/documents How to manage vehicle documents, service checklists, and other resources. The documents, notes, and checklist section provides centralized management of vehicle documentation, service checklists, and administrative resources. Organize, access, and maintain essential documentation for your professional operations. > [!NOTE] > > For each individual vehicle, you may also find documents and notes in its details view. See the [vehicles section](/handbook/professional/vehicles#notes-and-documents) for more information. ![OEM dashboard showing document management interface with categories and upload options](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/note/documents.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=fe30634ae951593a43ac0ed51f29b073) The documents and notes section corresponds to the "Documents & Checklists" menu item in the OEM Suite. Please refer to the [OEM Suite documentation](/handbook/oem/documents) for more details. > [!NOTE] > > In comparison to the OEM Suite, you may have limited access to certain features, depending on your organization's permissions and settings. # Ecosystem Source: https://docs.ctechnology.io/handbook/professional/ecosystem News articles, push messages, and support interactions. The ecosystem section manages communication channels, news distribution, and support interactions within the c.technology platform. ![OEM dashboard showing news article details with editing interface](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/ecosystem/news_article_single.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=d8ab097c42065fef8e7bcaafa78f4263) Note that this section corresponds to the "Channels" menu item in the OEM Suite. Please refer to the [OEM Suite documentation](/handbook/oem/channels) for more details. > [!NOTE] > > In comparison to the OEM Suite, you may have limited access to certain features, depending on your organization's permissions and settings. # Insights Source: https://docs.ctechnology.io/handbook/professional/insights Analysis of vehicle usage, performance metrics, and business analytics. The insights section provides comprehensive analytics and reporting tools to help you understand vehicle performance, optimize operations, and make data-driven business decisions. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/insights.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=cd3fdcc584b1751e936281c7c0fd6a69) The insights section corresponds to the "Insights" menu item in the OEM Suite. Please refer to the [OEM Suite documentation](/handbook/oem/insights) for more details. > [!NOTE] > > In comparison to the OEM Suite, you may have limited access to certain features, depending on your organization's permissions and settings. # Professional Hub introduction Source: https://docs.ctechnology.io/handbook/professional/introduction Getting started as a professional partner (dealer, service provider, rental) on the c.technology platform. The professional Hub is for companies such as vehicle dealers, service providers, maintenance facilities, and fleet operators. You can use the c.technology platform to manage customer vehicles, streamline operations, and deliver exceptional service. ![Professional dashboard showing vehicle management overview with fleet status and navigation menu](https://mintcdn.com/ctechnologyag/2fKpZfAzamlnzOS6/images/handbook/professional/dashboard.png?fit=max\&auto=format\&n=2fKpZfAzamlnzOS6\&q=85\&s=ff0e3ae874f5355f359c8b18a8165581) The dashboard upon login highlights key metrics such as vehicle status alerts, vehicle usage, and currently important issues. On the left side, you see the main navigation menu that allows you to access all sections of the Professional Hub. Click the icon if the menu is hidden. ## Sections of the Professional Hub The Professional Hub is divided into the following sections: > **[Vehicle overview](/handbook/professional/vehicles)** > > Check the status of all vehicles under management. > **[Clients](/handbook/professional/clients)** > > Overview of all customers and their vehicles. > **[Ecosystem](/handbook/professional/ecosystem)** > > News articles, push messages, and support interactions. > **[Services](/handbook/professional/services)** > > Custom professional services, such as hibernation, preparations, and more. > **[Maintenance](/handbook/professional/maintenance)** > > Maintenance management, service history, and error definitions. > **[Insights](/handbook/professional/insights)** > > Analysis of vehicle usage. > **[Documents and checklists](/handbook/professional/documents)** > > Vehicle documents, service checklists, and other resources. > **[Organization settings and users](/handbook/professional/settings)** > > How to structure teams and organization settings. # Maintenance Source: https://docs.ctechnology.io/handbook/professional/maintenance How to manage maintenance as a professional partner. The maintenance section provides tools for tracking, scheduling, and managing vehicle maintenance across your customer fleet. Upon selecting "Maintenance" from the main menu, you will see an overview of all vehicles with their maintenance status, upcoming maintenance tasks, and maintenance history. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/maintenance.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=487d7ff320fb47ae56805b0a93dcec3a) The upcoming maintenance is computed by an extrapolation of the vehicle's current distance, operation hours, and time since last maintenance, compared to the configured maintenance intervals. You can click on any vehicle in the maintenance table to access detailed maintenance management for that specific vehicle. For information regarding the detailed maintenance view of an individual vehicle, please refer to the [vehicle overview section](/handbook/professional/vehicles#errors%2C-maintenance-and-support). # Notifications Source: https://docs.ctechnology.io/handbook/professional/notifications Notify your team when something happens to a selection of your vehicles, by web, app and email. The **Notifications** section lets your organization define rules once and have the right people on your team informed when something happens to your vehicles. Instead of every team member configuring every vehicle, you describe the event, the vehicles and the recipients in one place. Notification rules of an organization are separate from the personal notification rules that every user can set up for a single vehicle, which are described in [Notifications and alerts](/handbook/private/notifications). Personal rules are not affected. > [!NOTE] > > The section is available to organizations that have notification rules enabled. Which team members can see and change rules depends on their role, see [Who can see and edit rules](#who-can-see-and-edit-rules). ## What a notification rule is A notification rule combines four things: * **A trigger**, the event the rule reacts to, for example "Battery level below 20 %" or "Fault code reported". * **The vehicles** the rule watches. The selection stays current by itself: new vehicles that match are included automatically. * **The recipients**, up to 25 team members, and for each person the channels they are notified through. * **Settings** such as the priority, a cooldown, an optional time window and whether the rule is active. The overview lists all rules of your organization with their name, trigger, the vehicles they apply to, the number of recipients, their status (active or paused) and the time of the last change. You can search the list and filter it by trigger. ## Triggers The trigger is chosen in the first step of the editor. The triggers are grouped as in the app. **Telemetry thresholds** react when a measured value falls below or rises above a threshold you set: * Battery voltage * Battery level * Fuel level * Temperature * Distance from home **Vehicle events** react when something happens to a vehicle. They need no further settings: * Ignition switched on * Ignition switched off * Vehicle starts moving * Vehicle towed or tilted * Device power disconnected * Battery low * Vehicle offline * Arrived home * Left home * Shore power disconnected * Shore power connected * Put into the water * Taken out of the water * Range critical * Fuel not full on return **Fault codes** react when a fault code is reported for a vehicle. You can choose a minimum severity, or react to any severity. **Maintenance** reacts when a maintenance task becomes due soon or overdue, whether it is due by time, distance or operating hours. **Geofences** react when a vehicle enters or leaves one of your organization's geofences, see [Geofence rules](#geofence-rules). For a threshold trigger, choose the condition ("Falls below" or "Rises above") and the threshold value. The rule notifies when the value crosses the threshold, not on every update while it stays beyond it. ## Geofence rules A geofence rule notifies your team when a vehicle enters ("Geofence entered") or leaves ("Geofence left") one of your organization's geofences. * **One geofence per rule.** In the editor you choose the geofence the rule watches. The picker is available to team members who may see the organization's geofences. * **Vehicles.** The rule applies to the vehicles of that geofence, shown as "All vehicles of the geofence". In the vehicles step you can narrow this to a subset, for example one vehicle type. The editor then shows how many vehicles are covered, for example "3 of 12 vehicles". A rule never covers vehicles the geofence does not apply to. * **Once per crossing.** Each entry or exit is reported once per vehicle, however many rules or recipients there are. The default cooldown is 5 minutes, so a vehicle moving along the edge of a geofence does not flood your team. Priority, time window and channels work as for every other rule. * **Who is notified.** Only team members who may see the organization's geofences and where the vehicle is receive the notification. Members who may not are marked "May not see the geofences" and must be removed before you can save the rule. * **Deleting a geofence.** When you delete a geofence, the rules that use it are switched off, not deleted. The delete dialog tells you how many rules are affected. Such a rule is marked "Geofence deleted" and can only be switched on again after you choose a geofence that still exists. The entries and exits also appear in the vehicle logbook. ## Choosing vehicles In the second step you choose which vehicles the rule applies to: * **All vehicles** of your organization. * **A vehicle category**, **family** or **type**. * **Chosen vehicles**, a selection you pick one by one. The editor shows the effective vehicle count next to the selection, so you can see how many vehicles the rule currently covers. Because the selection is kept up to date automatically, a rule for a category also covers vehicles that join the category later. ## Expected notifications and the noisy rule warning Next to the vehicle selection, the editor shows an estimate under **Expected notifications**: about how many notifications a day each recipient will receive, based on the trigger, the number of vehicles and the cooldown. Triggers without an estimate show "No estimate for this trigger yet." If a rule is likely to produce a flood of notifications, a warning appears, for example "This rule may create about 400 notifications a day for each recipient (100 vehicles × about 4 per vehicle and day)". The warning also appears in the summary and as an icon in the overview. There is no hard limit: you can still save the rule, for example because a large fleet with a frequent trigger is intended. To reduce the volume, select fewer vehicles, choose a longer cooldown, restrict the rule to a time window or pick a less frequent trigger. ## Recipients and channels In the third step, choose the team members who are notified, up to 25 per rule. Only members who have access to the organization can be selected. Members without access are marked "No access to the organization" and must be removed before you can save. For each recipient you choose the channels: | Channel | What it does | | - | - | | **History** | Every notification is always kept in the person's notification history. This cannot be switched off. | | **Web** | A notification in the web application. | | **App** | A push notification on the person's mobile device. | | **Email** | An email. | Emails are bundled: a person receives at most one email from your organization every 5 minutes, listing everything that happened in between. The email carries your organization's name and logo and offers an unsubscribe link for each rule. When a recipient unsubscribes from the emails of a rule, the editor shows "Unsubscribed on" for that person and you cannot switch the emails back on for them. Only the recipient can do that, see [Notifications and alerts](/handbook/private/notifications#organization-notifications). Until you add team members, nobody is notified by the rule. If a team member is removed from your organization, they no longer receive notifications from your rules. ## Settings The first step also holds the settings of the rule: * **Name** and an optional **description**. The name is shown to recipients as the title of the notification. * **Notification priority**: Low, High or Alert. High and Alert also show a pop-up to recipients who are using the web app. * **Cooldown**: the shortest time between two notifications of this rule for the same vehicle. You can keep the default of the trigger (shown in brackets), choose no cooldown, or choose a duration from one minute up to seven days. * **Only within a time window**: notify only between a start and an end time of the day, in a time zone you choose. A start later than the end wraps past midnight, for example 22:00 to 06:00. * **Active**: a paused rule keeps its settings but notifies nobody. A summary of the rule is shown before you save it. ## Creating, editing and deleting rules Click **New notification rule** to open the editor. It guides you through three steps, **Trigger**, **Vehicles** and **Recipients**, followed by a summary. Any problem, such as a missing name or threshold, is shown with a short message before you can continue. Use the edit icon in the overview to change a rule and the trash can icon to delete it. Deleting asks for confirmation. A deleted rule stops notifying immediately, and the notifications it already created stay in the recipients' histories. To stop a rule temporarily without losing its settings, pause it instead of deleting it. ## Who can see and edit rules * Team members with the **view** permission see the Notifications section and the list of rules. * Team members with the **edit** permission can also create, change and delete rules. * Administrators, standard, service, marketing and engineering users can view and edit. Read-only users can view only. Receiving notifications does not need either permission: any team member with access to the organization can be chosen as a recipient. For the roles of your team, see [Team management](/handbook/oem/team). > [!NOTE] > > The vehicle events created by thresholds of your organization are visible only to members of your organization. Vehicle owners and other organizations that also hold the vehicle do not see them. # Services Source: https://docs.ctechnology.io/handbook/professional/services Activate and use professional vehicle services. **Vehicle services** are specialized workflows designed for professional partners to manage various vehicle-related tasks efficiently. These services include vehicle preparation, launch services, hibernation management, and other custom services tailored to your operational needs. The services can generally be purchased and activated through the in-app store. If you want access to a specific service that is not listed in the store, please contact your account manager or c.technology support. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/service-store.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=ed42968e1de845f34e138403657144ad) Once activated, services can be accessed through the **Services** menu item in the main navigation. Each service consists of a service management view, a calendar, a "vehicles active in service" overview, a logging section, and a settings tab. While the management view may differ between services, the calendar, active vehicles, log, and settings tabs are usually consistent across all services. Click on "Configure" in the active vehicles tab to set up the service for specific vehicles. The following is an example from the **Vehicle Preparation** service, which is used to prepare vehicles for handover to customers. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/service-example.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=026e700e671a2b37a29387d8cc706685) # Organization settings and users Source: https://docs.ctechnology.io/handbook/professional/settings How to structure teams and organization settings. The settings section provides tools for configuring your organization, managing team members, and customizing platform behavior to match your operational requirements. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/team.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=789ac7d51f0556a9bc8abcf8a378dab7) As the team settings and user management are shared with the OEM Suite, please refer to the [OEM Suite documentation](/handbook/oem/team) for detailed information on managing users and teams. ![](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/settings_organization.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=9fd8bd1c4388786b4acfefe20db46da5) Similarly, as most of the settings are shared with the OEM Suite, please refer to the [OEM Suite documentation](/handbook/oem/settings) for detailed information on each setting. > [!NOTE] > > In comparison to the OEM Suite, you may have limited access to certain features, depending on your organization's permissions and settings. # Vehicle overview Source: https://docs.ctechnology.io/handbook/professional/vehicles Monitor and manage all vehicles under your organization's oversight The vehicle overview provides a central hub for monitoring all vehicles under management, including your own fleet and customer vehicles. This section displays real-time status, operational metrics, and management controls. You can access the vehicle overview by selecting "Vehicles" from the main menu (may also be called "Boats", "Motorcycles", etc. depending on your vehicle type). ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicles.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=fac6595b9110614ea46d550fe14b9aa2) The vehicle table shows all vehicles with their key information: * Vehicle name and type (incl. organizational ids or names) * Connection status (online/offline) * Subscription status (active/inactive) * Battery / fuel level * Errors and warnings * Distance traveled and operation hours You can use various filters and search options to find specific vehicles or groups of vehicles based on criteria like status, name, errors, etc. Depending on if this is your own vehicle or a client vehicle under management, a tag "client" will be shown next to the vehicle name. You have less access rights for client vehicles, e.g. you cannot edit all vehicle settings, see a vehicle's position, etc. > [!NOTE] > > Depending on your access rights, you may also see the vehicle in the sidebar. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-client.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=e864110ccc9f0f524dc0da0e44429b36) Clicking on a vehicle opens the vehicle details view, where you can see more detailed information and manage the vehicle. This includees a "data" section, where individual data points (that you have access to) are visible. Clicking on a numerical data point opens a chart view with historical data. Below the data section, you can find a usage overview that shows distance traveled and operation hours in a given year. ## Notes and documents The notes and documents section allows you to manage vehicle-specific notes and documents. This includes notes that are assigned to an individual day ("Calendar messages"), as well as general notes that are not date-specific. Additionally, this will show documents uploaded by you, or given access to by a manufacturer. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-notes.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=171bea90f6082d1fc790a105d602ec65) ## Errors, maintenance and support The errors, maintenance, and support section provides an overview of current vehicle errors, maintenance status, and support tickets. The error summary tab shows all current and past errors. Clicking on an error opens a detailed view with more information about the error, possible causes, and recommended actions. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-errors.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=eaa37768557a44c2235ddf1f4b6b4e4d) The maintenance tab shows the current maintenance status, upcoming maintenance tasks, and maintenance history. You can complete maintenance tasks directly from this view by clicking on the "Mark as done" button, or by "Add past maintenance" for maintenance that was done outside of the system. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-maintenance.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=ddffd7c8a14888df2aa10b9ccdbce599) The support tab shows all support tickets related to the vehicle. Clicking on a ticket opens the detailed view, where you can see the conversation history and add new messages. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-support.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=4e38e80b18402063065207885b52f1ce) > [!NOTE] > > You may not have access to all support tickets, depending on your organization's permissions and settings. ## Settings and notifications In order to assist your customers with vehicle configuration, you can access certain vehicle settings directly from the vehicle details view. This includes settings like vehicle name, access, subscription, sensor and actuator configuration, home locations, display settings, etc. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-settings.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=20e155d493d42c142356944cf2ef1f20) Additionally, you can configure notification settings for the vehicle. > [!NOTE] > > The notification settings are specific to your *personal* user account, and do not affect the vehicle or other users. ![](https://mintcdn.com/ctechnologyag/e16UvwlnDTU4Am6H/images/handbook/professional/vehicle-notifications.png?fit=max\&auto=format\&n=e16UvwlnDTU4Am6H\&q=85\&s=f78591307e8c151b015a9e03959e23e1) The notification screen shows all past notifications for the vehicle. Clicking on "Mark as read" will mark all notifications as read. # Mains detector Source: https://docs.ctechnology.io/hardware/auxiliary/mains-detector Documentation of the mains detector / power supply monitoring device. The mains detector is a device used to monitor the presence of a mains electricity in a given location. This is common in marine applications to detect if shore power is connected to a boat and thus battery depletion is avoided and on-board systems can be powered directly from shore power (fridges, heating, etc.). ## Features c.technology offers a mains detector device that can be connected to our tracking devices via digital inputs. The mains detector has the following features: * Detects the presence of mains electricity (typically 110V or 230V AC). * Provides a digital signal that can be read by compatible tracking devices. * Compact and easy to install. * Suitable for marine and other applications. ## Installation instructions Please download the printable [installation manual](/documents/hardware/mains-detector-installation-manual.pdf) for detailed installation instructions. # Temperature (BLE) Source: https://docs.ctechnology.io/hardware/auxiliary/temperature Documentation of the temperature sensors using BLE (Bluetooth Low Energy). Bluetooth Low Energy (BLE) temperature sensors can be used with compatible tracking devices to monitor temperature in various environments, such as vehicles, containers, or storage areas. ## Supported sensors c.technology supports the following BLE temperature sensors: * **EYE sensors**: Sealed Bluetooth sensors that can read temperature and humidity. Compatible with Teltonika products. * **Ruuvi sensors**: Versatile Bluetooth sensors that can read temperature, humidity, air pressure, and acceleration, with a replacable battery. Compatible with Astra Telematics. ## Features * Wireless temperature monitoring via Bluetooth Low Energy (BLE). * Easy integration with compatible tracking devices. * Suitable for various applications, including automotive, marine, and logistics. ## Installation instructions Please download the printable [installation manual](/documents/hardware/temperature-sensor-installation-manual.pdf) for detailed installation instructions. # Water sensor Source: https://docs.ctechnology.io/hardware/auxiliary/water Documentation of the water sensor device. A water sensor is a device used to detect the presence of water in a given location. The water sensor supplied by c.technology works using a floating mechanism that triggers a switch when water is detected. > [!NOTE] > > Generally, you should not expose electric contacts directly to water due to > galvanic corrosion. The water sensor prevents this by using the floating > mechanism and not exposing contacts directly to water. ## Features c.technology offers a water sensor device that can be connected to our tracking devices via digital inputs. The water sensor has the following features: * Detects the presence of water by pushing up a floating mechanism. * Provides a digital signal that can be read by compatible tracking devices. * Compact and easy to install. ## Installation instructions Please download the printable [installation manual](/documents/hardware/water-sensor-installation-manual.pdf) for detailed installation instructions. # Astra Telematics AT241/242 Source: https://docs.ctechnology.io/hardware/devices/at241 Documentation and installation instructions for Astra Telematics AT241/242. The Astra Telematics AT241/242 is a compact and cost-effective telematics device suitable for various vehicle types, including cars, motorcycles, and boats. It offers essential features such as GPS tracking, cellular connectivity, and OBD2 support. ## Data sheet The following excerpt is the most relevant information for marine and on-road applications from the [official data sheet](https://astratelematics.com/wp-content/uploads/2020/12/AT241-data-sheet.pdf). Please always refer to the official documentation for the most accurate and up-to-date information. | Feature | Specification | | - | - | | Mobile Network Communications | LTE-Cat 1 (4G) - others possible | | Maximum Operating Voltage | 65.0V | | Antennas | Internal | | BLE (Bluetooth) Option | Yes | | SIM Card Format | Micro | | Accelerometer / tamper sensor | Yes | | Battery Capacity (internal) | 510mAh (6 days low power mode, 24h reporting) | | Battery Life (LP mode, 24hr reporting) | 6 days | | Ingress Protection | IP67 | | Digital Ins / Outs | 6 / 5 | | ADC Inputs | 2 | | CAN bus | Yes ([NMEA2000 support](#nmea-2000-support-scope), custom protocols) | ## Installation instructions Please download the printable [installation manual](https://drive.google.com/file/d/1oLkxR1L4xYe1_8vz3mJgud-0nFMd8S7T/view?usp=drive_link) for detailed installation instructions. ## NMEA 2000 support scope > **Disclaimer**\ > Our NMEA 2000 integration **natively supports only the items listed below**. Any additional parameters, multi-engine/tank setups, or proprietary PGNs/features must be reviewed and agreed separately (feasibility, timeline). | Category | Property | | - | - | | Battery | State of Charge % (DC type 0) | | | State of Health % (DC type 0) | | | Battery Capacity (Ah, DC type 0) | | | Charger Enable / Disable | | | Time to Empty | | | Distance to Empty | | Fuel & Trip | Fuel Level % (type 0) | | | Fuel Rate | | | Trip Fuel Used | | | Trip Run Time | | Engine | Oil Level % (type 4) | | | Engine Oil Pressure | | | Engine Oil Temperature | | | Engine Temperature | | | Alternator Voltage | | | Engine Coolant Pressure | | | Fuel Pressure | | | Percent Engine Load | | | Percent Engine Torque | | | Total Engine Hours | | | Engine Discrete Status 1 | | | Engine Discrete Status 2 | | Environment/Depth | Water Depth at Transducer | | | Water Depth Transducer Offset | | | Wind Speed | | | Air Temperature | **Notes** * Applies to **one engine and one tank**. * Compatibility depends on the vessel network publishing these PGNs per NMEA 2000 conventions. * Extensions (e.g., multiple engines/tanks, additional sensors, custom/proprietary PGNs) require a separate technical discussion. *“NMEA 2000” is a trademark of the National Marine Electronics Association (NMEA).* # Teltonika FMC001/003 Source: https://docs.ctechnology.io/hardware/devices/fmc001 Documentation and installation instructions for Teltonika FMC001/003. The Teltonika FMC001/003 is a compact and plug-and-play (due to its OBD2 form factor) GPS tracking device designed for various vehicle types, including cars, motorcycles, caravans, etc. It offers essential features such as GPS tracking, cellular connectivity, and OBD2 support. ## Data sheet The following excerpt is the most relevant information for marine and motorcycle applications from the [official data sheet](https://www.teltonika-gps.com/products/trackers/obd-data/fmc003). Please always refer to the official documentation for the most accurate and up-to-date information. | Feature | Specification | | - | - | | Mobile Network Communications | LTE(CaT1) / 2G(GSM/GPRS) | | Maximum Operating Voltage | 30.0V | | Antennas | Internal | | BLE (Bluetooth) Option | Yes | | SIM Card Format | Micro | | Accelerometer / tamper sensor | Yes (however, device usually is off) | | Battery Capacity (internal) | 170mAh | | Power consumption | 33mA\@12V nominal, 3-5mA\@12V sleep | | Ingress Protection | No | | Digital Ins / Outs | 0 /0 | | ADC Inputs | 0 | | CAN bus | Yes (only OBD2 support) | ## Installation instructions Please download the printable [installation manual](https://drive.google.com/file/d/1QG5x5damVvxnKm5lzqyILvSgI8HtPvQP/view?usp=sharing) for detailed installation instructions. # Teltonika FMC130/230 Source: https://docs.ctechnology.io/hardware/devices/fmc130 Documentation and installation instructions for Teltonika FMC130/230. The Teltonika FMC130 is a versatile GPS tracking device designed for automotive, agricultural, marine, and motorcycle applications. It features robust connectivity options, multiple input/output capabilities, and supports various sensors for comprehensive vehicle monitoring. ## Data sheet The following excerpt is the most relevant information for marine and motorcycle applications from the [official data sheet](https://www.teltonika-gps.com/products/trackers/advanced/fmc130). Please always refer to the official documentation for the most accurate and up-to-date information. | Feature | Specification | | - | - | | Mobile Network Communications | LTE (CaT1) / 2G (GSM/GPRS) | | Maximum Operating Voltage | 30.0V | | Antennas | Internal | | BLE (Bluetooth) Option | Yes | | SIM Card Format | Micro or eSIM | | Accelerometer / tamper sensor | Yes | | Battery Capacity (internal) | 170mAh | | Power consumption | 33mA\@12V nominal, 3-5mA\@12V sleep | | Ingress Protection | IP67 (FMC230) | | Digital Ins / Outs | 3 / 3 | | ADC Inputs | 2 | | CAN bus | Yes (no custom protocols) | ### Temperature sensors The FMC130/230 supports BLE EYE sensors for temperature monitoring. For more information, please refer to the [temperature (BLE) documentation](/hardware/auxiliary/temperature). ## Installation instructions Please download the printable [installation manual](https://drive.google.com/file/d/1S3hYfM4uICxazz7ecn4TyVPuOyPvsguN/view?usp=sharing) for detailed installation instructions. # Teltonika FMC640/650 Source: https://docs.ctechnology.io/hardware/devices/fmc640 Documentation and installation instructions for Teltonika FMC640/650. The Teltonika FMC640/650 is an advanced GPS tracking device designed for heavy-duty vehicles, including trucks, buses, and construction machinery. It features robust connectivity options via external antennas, multiple input/output capabilities, and supports various sensors for comprehensive vehicle monitoring. ## Data sheet The following excerpt is the most relevant information for marine and motorcycle applications from the [official data sheet](https://www.teltonika-gps.com/products/trackers/professional/fmc650). Please always refer to the official documentation for the most accurate and up-to-date information. | Feature | Specification | | - | - | | Mobile Network Communications | LTE (CaT1) / 2G (GSM/GPRS), LTE Cat M1 available as FMM650 | | Maximum Operating Voltage | 32.0V | | Antennas | External for GSM and GPS | | BLE (Bluetooth) Option | Yes | | SIM Card Format | Dual SIM or eSIM | | Accelerometer / tamper sensor | Yes | | Battery Capacity (internal) | 550mAh | | Power consumption | 45mA\@12V nominal, 4-11mA\@12V sleep | | Ingress Protection | IP41 | | Digital Ins / Outs | 4 / 4 | | ADC Inputs | 4 | | CAN bus | Yes ([NMEA2000 support](#nmea-2000-support-scope), custom protocols) | ### Temperature sensors The FMC640/650 supports BLE EYE sensors for temperature monitoring. For more information, please refer to the [temperature (BLE) documentation](/hardware/auxiliary/temperature). ## Installation instructions Please contact our Support [support@ctechnology.io](mailto:support@ctechnology.io) if you need any installation guidance or instructions. ## NMEA 2000 support scope > **Disclaimer**\ > Our NMEA 2000 integration **natively supports only the items listed below**. Any additional parameters, multi-engine/tank setups, or proprietary PGNs/features must be reviewed and agreed separately (feasibility, timeline). | Category | Property | | - | - | | Battery | State of Charge % (DC type 0) | | | State of Health % (DC type 0) | | | Battery Capacity (Ah, DC type 0) | | | Charger Enable / Disable | | | Time to Empty | | | Distance to Empty | | Fuel & Trip | Fuel Level % (type 0) | | | Fuel Rate | | | Trip Fuel Used | | | Trip Run Time | | Engine | Oil Level % (type 4) | | | Engine Oil Pressure | | | Engine Oil Temperature | | | Engine Temperature | | | Alternator Voltage | | | Engine Coolant Pressure | | | Fuel Pressure | | | Percent Engine Load | | | Percent Engine Torque | | | Total Engine Hours | | | Engine Discrete Status 1 | | | Engine Discrete Status 2 | | Environment/Depth | Water Depth at Transducer | | | Water Depth Transducer Offset | | | Wind Speed | | | Air Temperature | **Notes** * Applies to **one engine and one tank**. * Compatibility depends on the vessel network publishing these PGNs per NMEA 2000 conventions. * Extensions (e.g., multiple engines/tanks, additional sensors, custom/proprietary PGNs) require a separate technical discussion. *“NMEA 2000” is a trademark of the National Marine Electronics Association (NMEA).* # Hardware introduction Source: https://docs.ctechnology.io/hardware/introduction How c.technology can assist you with hardware decisions and installation. While c.technology does not manufacture hardware, we offer expert guidance on selecting and installing compatible devices for your specific use case, in addition to a range of devices working out of the box with our platform. You can order supported devices via [shop.ctechnology.io](https://shop.ctechnology.io) or through our partners. ## Out-of-the-box telematics units The following devices are fully supported by c.technology and can be used for various applications including boats, motorcycles, and stationary asset tracking. * **Astra Telematics AT241/242**: Compact, powerful, and cost-effective vehicle tracker with NMEA2000 (marine) support. * **Teltonika FMC130/230**: Multi-purpose tracking device for boats and motorcycles. * **Teltonika FMC640**: Advanced tracker with enhanced features, such as NMEA2000 support and external antennas. * **Teltonika FMC001/003**: OBD2 dongle for easy installation in motorcycles and cars. * **Other Astra Telematics and Teltonika models**: Various models available for different use cases. ## Auxiliary sensors In addition, we offer auxiliary sensors that extend monitoring capabilities: * **Temperature Sensors**: Environmental and engine temperature monitoring via Bluetooth. * **Water Detection**: Bilge water and leak detection systems. * **Mains Detection**: Shore power connection monitoring. ## Installation and operation requirements The following points should be considered when installing and operating telematics devices: * **Power supply**: Direct connection to vehicle's electrical system (12V/24V). Power consumption usually 35mA\@12V during operation, and 0.1-3.5mA\@12V in sleep mode (depending on device and configuration). * **Installation safety**: Proper fusing and weatherproof connections required. * **Cellular network**: 2G/4G LTE connectivity for data transmission (depending on location and device). * **SIM card**: We can supply or assist with SIM cards for cellular connectivity. Needs data plan for IoT usage. * **Antenna placement**: GPS and cellular antennas require clear sky view. * **Temperature range**: Operating range typically -40°C to +85°C. * **Vibration resistance**: Marine and automotive vibration specifications. > [!NOTE] > > In the future (Q2 2026), we will support devices that can be powered from 48V > systems, such as e-bikes and e-scooters. # Recommendations Source: https://docs.ctechnology.io/hardware/recommendations Our recommendations for hardware and related solutions. An overall distinction should be made between marine and on-road vehicles. ## Marine solutions Commonly, marine telematics devices should meet the following criteria: * **Waterproof**: IP67 or higher rating. * **NMEA2000 support**: For integration with marine electronics (larger and newer vessels). * **Low power consumption**: To avoid draining the boat's battery during periods of inactivity. * **Antenna or device placement**: Depending on the size and build of the boat, external antennas may be required for optimal GPS and cellular reception. * **Auxiliary sensors**: Such as water detection (bilge monitoring) and mains detection (shore power monitoring). The Astra Telematics AT241/242 is suitable for most marine applications, due to its compact size, NMEA2000 support, and cost-effectiveness. For larger vessels or more advanced use cases, the Teltonika FMC640 is a robust choice with enhanced features (similar NMEA2000 support, external antennas). ## 2-wheelers For 2-wheeler vehicles, the following criteria are important: * **Compact size**: To fit the limited space available on motorcycles and scooters. * **Vibration resistance**: To withstand the harsher conditions and vibrations experienced on 2-wheelers. * **GPS accuracy**: Enhanced GPS capabilities for better tracking and navigation. * **Low power consumption**: To minimize battery drain, especially on vehicles with smaller batteries. The Astra Telematics AT241/242 is suitable for motorcycles and scooters, as it offers a good balance of size, features, cost, and OBD2 support. For a pure OBD2 solution, the Teltonika FMC001/003 is a convenient option, allowing for easy installation and removal. Note that in this case, the device is powered via OBD2 port, which prevents the device from being used as a theft deterrent when the vehicle is off - on the other hand, installation is very simple, does not require any wiring, and does not drain the vehicle's battery when parked. > [!NOTE] > > With Euro5 and Euro6 standards, many modern motorcycles now support OBD2, > making the FMC001/003 a viable option for a wide range of bikes. ## Other on-road vehicles For other on-road vehicles, such as cars, vans, and trucks, the following criteria should be considered: * **OBD2 / FMS support**: For easy installation and access to vehicle data. * **Plug-and-play**: Simple installation and configuration. The Astra Telematics AT241/242 with an OBD2 adapter is a solid choice for general vehicle tracking, due to its compact size and cost-effectiveness. For more advanced use cases, such as fleet management or vehicles requiring additional features, the Teltonika FMC130/230 or FMC640 are robust choices with enhanced capabilities (FMS integration, external antennas). # c.technology platform Source: https://docs.ctechnology.io/index A batteries-included cloud platform for vehicle digitalization and fleet management. ![c.technology logo](https://mintcdn.com/ctechnologyag/NPQ2ln3oN-_JqwFH/logo/ctechnology-light.png?fit=max\&auto=format\&n=NPQ2ln3oN-_JqwFH\&q=85\&s=a2b2602fb0b3413f4f112b8cbbf5377a) The c.technology platform is a comprehensive cloud-based solution for vehicle management and data handling, designed to serve vehicle manufacturers (OEMs), professional partners (dealers, maintenance, rentals), individual vehicle owners, and their interactions with each other. ## Platform Overview At its core, the platform processes vehicle data, and gives secure access to different parties, helping them collaborate effectively. All the data is processed in real-time, providing insights, maintenance tracking, fleet management, and much more across a wide range of vehicles: boats, motorcycles, specialist vehicles, trucks, and even cars. ![OEM dashboard](https://mintcdn.com/ctechnologyag/F3J2cYsfyMfpXCZX/images/handbook/oem/dashboard.png?fit=max\&auto=format\&n=F3J2cYsfyMfpXCZX\&q=85\&s=a216dd761e986f6768ac0736758efab0) ## Who Uses c.technology * **OEMs (Vehicle Manufacturers)**: The *OEM Suite* provides vehicle post-production management, including data management, customer interactions, maintenance, support, engineering optimization feedbacks, firmware updates, and more. * **Professional Partners**: The *Professional Hub* offers fleet management for rental companies and custom vehicle insights for service providers and dealerships, tightly integrated with OEM data and systems for improved maintenance and support. * **Private Owners**: The *Private App* is a modern and convenient way for private owners to interact with their vehicles and support partners through Android and iOS apps, as well as a web dashboard for deeper insights. ## Documentation structure This documentation is structured into the following sections: > **[Handbook](/handbook/interactions)** > > A complete user guide for all platform interfaces. > **[Developer guides](/developer)** > > In-depth explanations of the platform and its APIs. > **[Hardware](/hardware/introduction)** > > Guidelines for installing recommended hardware. > **[REST API](/api-reference/introduction)** > > Documentation of the REST API and SDKs. > **[AsyncAPI](/asyncapi-reference/introduction)** > > Documentation of the real-time API. > **[Changelog](/changelog/api)** > > Complete changelog of all platform components. ## Getting Started Please use the sections above if you want more in-depth and technical information. If you are a user of the web or iOS / Android applications, continue here: * [OEM introduction](/handbook/oem/introduction) - To get started as an OEM employee. * [Professional partner introduction](/handbook/professional/introduction) - To get started as a professional vehicle owner or fleet manager. * [Private owner introduction](/handbook/private/introduction) - To get started as a private vehicle owner.