Vehicle Control

Remotely control vehicle functions through the Daakey app during an active booking. These endpoints communicate with the vehicle's telematics hardware via the INVERS system to perform actions like locking, unlocking, and managing the engine immobilizer.

Vehicle control is a core feature of the keyless car sharing experience. Instead of physical keys, users control the vehicle entirely through their smartphone. Commands are sent over cellular networks to the vehicle's telematics unit, which then executes the requested action.

Access Control

Vehicle control is only available during an active booking where you are the authorized driver. Attempting to control a vehicle outside of your booking period will result in a 403 error.

Command Reliability

Commands are sent via cellular networks, so response time may vary (typically 2-10 seconds). If a command fails due to poor connectivity, the API will suggest when to retry. For best results, ensure you're in an area with good cellular coverage.

Lock Vehicle

Lock all doors of the vehicle.

Endpoint

INFO

POST /api/v1/client/vehicles/{id}/lock

Headers

Header	Value	Required
Accept	application/json	Yes
Authorization	Bearer {token}	Yes
X-Agency-Signature	{signature}	Yes

Example Request

curl -X POST https://api.daakey.com/api/v1/client/vehicles/1/lock \
  -H "Accept: application/json" \
  -H "Authorization: Bearer {token}" \
  -H "X-Agency-Signature: {signature}"

Success Response (200)

{
  "success": true,
  "message": "Vehicle locked successfully",
  "data": {
    "vehicle_id": 1,
    "action": "lock",
    "status": "completed",
    "timestamp": "2024-01-01T12:00:00Z"
  },
  "request_id": "uuid",
  "timestamp": "2024-01-01T00:00:00.000Z"
}

---

Unlock Vehicle

Unlock all doors of the vehicle.

Endpoint

INFO

POST /api/v1/client/vehicles/{id}/unlock

Example Request

curl -X POST https://api.daakey.com/api/v1/client/vehicles/1/unlock \
  -H "Accept: application/json" \
  -H "Authorization: Bearer {token}" \
  -H "X-Agency-Signature: {signature}"

Success Response (200)

{
  "success": true,
  "message": "Vehicle unlocked successfully",
  "data": {
    "vehicle_id": 1,
    "action": "unlock",
    "status": "completed",
    "timestamp": "2024-01-01T12:00:00Z"
  },
  "request_id": "uuid",
  "timestamp": "2024-01-01T00:00:00.000Z"
}

---

Start Engine

Enable the engine immobilizer, allowing the vehicle to start.

Endpoint

INFO

POST /api/v1/client/vehicles/{id}/start

Example Request

curl -X POST https://api.daakey.com/api/v1/client/vehicles/1/start \
  -H "Accept: application/json" \
  -H "Authorization: Bearer {token}" \
  -H "X-Agency-Signature: {signature}"

Success Response (200)

{
  "success": true,
  "message": "Engine start enabled",
  "data": {
    "vehicle_id": 1,
    "action": "start_engine",
    "status": "completed",
    "timestamp": "2024-01-01T12:00:00Z"
  },
  "request_id": "uuid",
  "timestamp": "2024-01-01T00:00:00.000Z"
}

---

Stop Engine

Disable the engine immobilizer (prevents restart).

Endpoint

INFO

POST /api/v1/client/vehicles/{id}/stop

Example Request

curl -X POST https://api.daakey.com/api/v1/client/vehicles/1/stop \
  -H "Accept: application/json" \
  -H "Authorization: Bearer {token}" \
  -H "X-Agency-Signature: {signature}"

Success Response (200)

{
  "success": true,
  "message": "Engine stop enabled",
  "data": {
    "vehicle_id": 1,
    "action": "stop_engine",
    "status": "completed",
    "timestamp": "2024-01-01T12:00:00Z"
  },
  "request_id": "uuid",
  "timestamp": "2024-01-01T00:00:00.000Z"
}

---

Error Responses

No Active Booking (403)

{
  "success": false,
  "message": "No active booking for this vehicle",
  "data": null,
  "request_id": "uuid",
  "timestamp": "2024-01-01T00:00:00.000Z"
}

Command Failed (500)

{
  "success": false,
  "message": "Vehicle command failed",
  "data": {
    "error": "Vehicle not responding",
    "retry_after": 30
  },
  "request_id": "uuid",
  "timestamp": "2024-01-01T00:00:00.000Z"
}

Notes

• Commands are sent via the INVERS telematics system
• Response time may vary based on cellular connectivity
• Commands have a timeout of 30 seconds
• If a command fails, retry after the specified delay