Skip to main content
POST
/
v1
/
trips
/
{sessionId}
/
pause
curl -X POST "https://api.bookovia.com/v1/trips/a1b2c3d4-e5f6-7890/pause" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bkv_live_0ef660a982f34f1fcb6a68d29c2d911379d3abf6b36282d9de77dd94c3391e74" \
  -d '{
    "reason": "fuel_stop",
    "location": {
      "latitude": 54.554678,
      "longitude": -1.3584913,
      "address": "Shell Petrol Station, Newcastle"
    },
    "metadata": {
      "fuel_type": "diesel",
      "planned_duration": "10_minutes"
    }
  }'

{
  "success": true,
  "trip_id": "a1b2c3d4-e5f6-7890",
  "status": "paused",
  "paused_at": "2026-04-14T20:45:30Z",
  "duration_before_pause": 1847,
  "distance_before_pause": 23.4,
  "pause_location": {
    "latitude": 54.554678,
    "longitude": -1.3584913,
    "address": "Shell Petrol Station, Newcastle"
  },
  "pause_reason": "fuel_stop",
  "message": "Trip paused successfully. Use resume endpoint to continue tracking."
}

Documentation Index

Fetch the complete documentation index at: https://docs.bookovia.com/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

Pauses an active trip, stopping location data collection and analytics processing while maintaining the trip session. The trip can be resumed later using the Resume Trip endpoint.

​
Path Parameters

​
sessionId
string
required
The unique identifier for the trip session to pause. This is the trip ID returned from the Start Trip endpoint.

​
Headers

​
X-API-Key
string
required
Your API key for authentication. Use your production key starting with bkv_live_
​
Content-Type
string
required
Must be application/json

​
Request Body

​
location
object
required
Required: Current location when pausing the trip. Location data is mandatory to ensure accurate trip event tracking.
Location Required: As of April 2024, the location field is required for all pause events. This ensures every trip event has complete location data and human-readable addresses for reporting and analytics.
​
reason
string
Optional reason for pausing the trip (e.g., “fuel_stop”, “rest_break”, “traffic_delay”)
​
metadata
object
Additional custom metadata about the pause event

​
Response

​
success
boolean
Indicates if the trip was successfully paused
​
trip_id
string
The unique identifier for the paused trip
​
status
string
Trip status, will be “paused”
​
paused_at
string
ISO 8601 timestamp when the trip was paused
​
duration_before_pause
number
Duration in seconds from trip start to pause
​
distance_before_pause
number
Distance traveled in kilometers before pause
​
pause_location
object
Location where the trip was paused
curl -X POST "https://api.bookovia.com/v1/trips/a1b2c3d4-e5f6-7890/pause" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bkv_live_0ef660a982f34f1fcb6a68d29c2d911379d3abf6b36282d9de77dd94c3391e74" \
  -d '{
    "reason": "fuel_stop",
    "location": {
      "latitude": 54.554678,
      "longitude": -1.3584913,
      "address": "Shell Petrol Station, Newcastle"
    },
    "metadata": {
      "fuel_type": "diesel",
      "planned_duration": "10_minutes"
    }
  }'

{
  "success": true,
  "trip_id": "a1b2c3d4-e5f6-7890",
  "status": "paused",
  "paused_at": "2026-04-14T20:45:30Z",
  "duration_before_pause": 1847,
  "distance_before_pause": 23.4,
  "pause_location": {
    "latitude": 54.554678,
    "longitude": -1.3584913,
    "address": "Shell Petrol Station, Newcastle"
  },
  "pause_reason": "fuel_stop",
  "message": "Trip paused successfully. Use resume endpoint to continue tracking."
}

​
Use Cases

  • Fuel Stops: Pause during refueling to exclude idle time from trip analytics
  • Rest Breaks: Separate actual driving from mandatory rest periods
  • Traffic Delays: Pause during extended traffic stops for accurate ETA calculations
  • Loading/Unloading: Exclude cargo handling time from driving performance metrics
  • Maintenance: Pause trips during vehicle maintenance or inspections

​
Important Notes

  • Only active trips can be paused (status: “active”)
  • Paused trips must be resumed or stopped, cannot be left indefinitely paused
  • Location tracking stops completely during pause periods
  • Analytics calculations exclude paused duration from trip metrics
  • Trip can be resumed from the same or different location