Business & Operations
This section covers operational and vehicle-related topics that go beyond pure API implementation. Use it when planning rollouts, handling vehicle-specific questions or defining support processes.
Vehicle access vs. vehicle start
Section titled “Vehicle access vs. vehicle start”Vehicle access and vehicle start are separate topics.
| Topic | Meaning |
|---|---|
| Vehicle access | Customer can lock or unlock the vehicle |
| Vehicle start | Customer can start or drive the vehicle |
| Keyless Start | Vehicle detects the original key without inserting it |
| Keyfob Power Control (KPC) | Power control for the original key inside the BLE Box |
Keyfob Power Control (KPC)
Section titled “Keyfob Power Control (KPC)”KPC is used when the original vehicle key remains inside the flinkey BLE Box and needs to be electronically controlled — especially relevant for Keyless Start vehicles.
The KPC adapter replaces the keyfob battery and allows the BLE Box to power/depower the key as needed during lock/unlock flows.
The exact setup depends on vehicle model, key type and installation concept. Involve flinkey before planning a KPC-dependent rollout.
Vehicle setup
Section titled “Vehicle setup”A flinkey integration may require vehicle-specific preparation:
- Original key placement and keybed compatibility
- Physical box installation and power supply
- BLE accessibility
- Key button mapping (lock / unlock / trunk)
- Keyless Start behavior
- Workshop or installation process
Recommended approach:
- Validate one representative vehicle type
- Confirm key and box setup
- Confirm lock, unlock and (if needed) start behavior
- Confirm support and fallback process
- Document vehicle-specific findings
- Repeat for each relevant vehicle type
Box Commands
Section titled “Box Commands”Box Commands extend the standard BLE access trigger with custom behavior — for example controlling the box lock state, querying status or reading NFC tag UIDs.
Box Commands are part of the mobile access flow, not REST API endpoints. They do not replace assignments. See the dedicated Box Commands guide for the full command reference, code examples and feedback parsing.
Operational fallback
Section titled “Operational fallback”Define what happens when digital access does not work as expected before go-live:
- Customer cannot unlock vehicle
- Mobile app has no network
- Phone Bluetooth disabled or battery empty
- BLE Box not found
- Assignment webhook reports failure
- Box or key setup requires support
Possible fallback concepts: customer support process, operations team intervention, alternative vehicle assignment, manual key handling or escalation to flinkey.
Support and diagnostics
Section titled “Support and diagnostics”Support teams need enough information to diagnose access issues without exposing secrets.
Recommended support information:
- Partner customer and vehicle references
- flinkey IDs (customer, car, user, assignment)
- Assignment status and last webhook result
- Mobile platform, app version, SDK version
- Sanitized error category and timestamp
Rollout checklist
Section titled “Rollout checklist”- Backend integration implemented (assignments + webhooks)
- Mobile access flow validated (Android and/or iOS)
- Representative vehicle type tested
- Key and box setup validated
- Lock/unlock behavior validated
- Vehicle start behavior validated (if required)
- Support process defined
- Fallback process defined
- Operational monitoring available
- Sensitive values not logged
When to involve flinkey
Section titled “When to involve flinkey”Contact flinkey before rollout if any of the following apply:
- New vehicle type or unclear key compatibility
- Keyless Start or KPC requirement
- Special box installation
- Box Commands required
- Fleet-scale rollout
- Repeated assignment or mobile access failures
- Unclear webhook behavior