Skip to main content
POST
/
v1
/
trips
/
{sessionId}
/
resume
curl -X POST "https://api.bookovia.com/v1/trips/a1b2c3d4-e5f6-7890/resume" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bkv_live_0ef660a982f34f1fcb6a68d29c2d911379d3abf6b36282d9de77dd94c3391e74" \
  -d '{
    "location": {
      "latitude": 54.556789,
      "longitude": -1.3601245,
      "address": "A1 Northbound, Newcastle"
    },
    "reason": "fuel_complete",
    "metadata": {
      "fuel_added": "45_litres",
      "break_duration": "8_minutes"
    }
  }'

{
  "success": true,
  "trip_id": "a1b2c3d4-e5f6-7890",
  "status": "active",
  "resumed_at": "2026-04-14T20:53:45Z",
  "total_pause_duration": 495,
  "pause_count": 1,
  "resume_location": {
    "latitude": 54.556789,
    "longitude": -1.3601245,
    "address": "A1 Northbound, Newcastle"
  },
  "distance_from_pause": 0.8,
  "message": "Trip resumed successfully. Location tracking and analytics restarted."
}

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

Resumes a previously paused trip, restarting location data collection and analytics processing. The trip continues from where it was paused, maintaining the original trip session.

​
Path Parameters

​
sessionId
string
required
The unique identifier for the paused trip session to resume. 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 resuming 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 resume events. This ensures every trip event has complete location data and human-readable addresses for reporting and analytics.
​
reason
string
Optional reason for resuming (e.g., “fuel_complete”, “break_ended”, “maintenance_finished”)
​
metadata
object
Additional custom metadata about the resume event

​
Response

​
success
boolean
Indicates if the trip was successfully resumed
​
trip_id
string
The unique identifier for the resumed trip
​
status
string
Trip status, will be “active”
​
resumed_at
string
ISO 8601 timestamp when the trip was resumed
​
total_pause_duration
number
Total time in seconds the trip was paused
​
pause_count
number
Number of times this trip has been paused/resumed
​
resume_location
object
Location where the trip was resumed
​
distance_from_pause
number
Distance in kilometers between pause and resume locations
curl -X POST "https://api.bookovia.com/v1/trips/a1b2c3d4-e5f6-7890/resume" \
  -H "Content-Type: application/json" \
  -H "X-API-Key: bkv_live_0ef660a982f34f1fcb6a68d29c2d911379d3abf6b36282d9de77dd94c3391e74" \
  -d '{
    "location": {
      "latitude": 54.556789,
      "longitude": -1.3601245,
      "address": "A1 Northbound, Newcastle"
    },
    "reason": "fuel_complete",
    "metadata": {
      "fuel_added": "45_litres",
      "break_duration": "8_minutes"
    }
  }'

{
  "success": true,
  "trip_id": "a1b2c3d4-e5f6-7890",
  "status": "active",
  "resumed_at": "2026-04-14T20:53:45Z",
  "total_pause_duration": 495,
  "pause_count": 1,
  "resume_location": {
    "latitude": 54.556789,
    "longitude": -1.3601245,
    "address": "A1 Northbound, Newcastle"
  },
  "distance_from_pause": 0.8,
  "message": "Trip resumed successfully. Location tracking and analytics restarted."
}

​
Use Cases

  • Completing Fuel Stops: Resume after refueling to continue journey tracking
  • Ending Rest Breaks: Continue trip after mandatory driver rest periods
  • Post-Maintenance: Resume tracking after vehicle maintenance or repairs
  • Traffic Clearance: Continue after extended traffic delays
  • Loading Complete: Resume after cargo loading/unloading activities

​
Important Notes

  • Only paused trips can be resumed (status: “paused”)
  • Trip maintains original session ID and start time
  • Pause duration is excluded from total trip time calculations
  • Analytics resume from the point of pause
  • Multiple pause/resume cycles are supported within a single trip

​
Validation Rules

  • Trip must exist and belong to the authenticated organization
  • Trip status must be “paused”
  • Resume location is optional but recommended for accurate routing
  • API will automatically detect location if not provided