PreStartPilot
Start free

PRESTARTPILOT API

Connect field operations to the rest of your business.

Use company-scoped credentials to connect assets, forms, inspections and GPS positions through the versioned PreStartPilot API.

CONNECTED BY DESIGN

Field data in.
Business systems out.

Select a connection to see how PreStartPilot can move operational data securely between the field and your existing systems.

PreStartPilotIntegration layerLIVE
SELECTED CONNECTION

REST API

Use revocable company API keys, idempotency protection and versioned endpoints to build reliable custom integrations.

Authorization: Bearer psp_live_…
Company-scoped and revocableCredentials are created by administrators, stored securely and can be revoked without changing user passwords.

Authentication

Create a credential under Company & API. The secret is displayed once and should be stored in a server-side secret manager. Grant only the read or write permissions the integration needs and choose an expiry date that matches your credential-rotation policy. Follow the API, webhooks and GPS integration guide for the complete setup and verification workflow.

Download the OpenAPI 3.1 specification

curl https://prestartpilot.com/api/v1/assets -H "Authorization: Bearer psp_live_…"

API endpoints

GET/api/v1/assetsCompany assets, operational state and QR tokens.
GET/api/v1/formsPublished form schemas and conditional rules.
GET/api/v1/submissionsInspection submissions and recorded answers.
POST/api/v1/submissionsSubmit a validated inspection and raise configured defects.
GET / POST/api/v1/positionsRead or submit authorised GPS positions.
POST/api/integrations/navixy/positionsImport Navixy/X-GPS state and webhook positions.
POST/api/integrations/samsara/positionsImport Samsara vehicle-stat GPS and usage snapshots.
POST/api/integrations/wialon/positionsImport Wialon current-unit positions or message batches.
POST/api/integrations/geotab/positionsImport Geotab DeviceStatusInfo or GetFeed batches.
POST/api/integrations/webfleet/positionsImport WEBFLEET.connect current object reports.
POST/api/integrations/motive/positionsImport Motive v1, v2 or v3 vehicle-location payloads.
POST/api/integrations/powerfleet/positionsImport Powerfleet Unity snapshots or legacy Fleet Complete asset positions.
POST/api/integrations/trackunit/positionsImport Trackunit Iris GeoJSON asset locations.
POST/api/integrations/verizon-connect/positionsImport Verizon Connect Reveal GPS webhook or polling positions.
POST/api/integrations/eroad/positionsImport EROAD Current Machine location and usage snapshots.
POST/api/integrations/digital-matter/positionsImport Digital Matter connector or Telematics Guru telemetry positions.

Submit an inspection

curl -X POST https://prestartpilot.com/api/v1/submissions \
  -H "Authorization: Bearer psp_live_…" \
  -H "Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000" \
  -H "Content-Type: application/json" \
  -d '{"templateId":"uuid","assetId":"uuid","answers":{"field_id":"pass"}}'

Idempotency keys prevent duplicate inspections when an integration retries a request. Required and conditional fields are validated against the published form version. Per-key throttles protect the service from accidental request loops; a limited request returns 429 with a Retry-After header.

Navixy / X-GPS connector

Register each device using its Navixy tracker ID, then send get_state, get_states or webhook payloads with the same company bearer key. Positions flow into the live map, trips and geofence engine.

Samsara connector

Register each tracker using its Samsara vehicle ID, then submit the data array returned by the vehicle-stats snapshot API. GPS positions, preferred OBD or GPS odometer readings and engine seconds are normalised for maps, geofences and maintenance schedules.

PreStartPilot GPS Tracking

Compatible tracking hardware connects to PreStartPilot GPS Tracking using its unique device ID. Once linked to an asset, positions appear in the live fleet map, trip history and geofence events.

Wialon connector

Register each tracker using its Wialon unit ID, then send current unit data or a unit message batch with the same company bearer key. Timestamps, coordinates, speed, course, altitude and ignition are normalised into the connected fleet record.

Geotab connector

Register each tracker using its Geotab device ID, then send current DeviceStatusInfo records or incremental GetFeed data. Location, speed, bearing, driving and communication state are normalised for the live fleet, trips and geofence engine.

Webfleet connector

Register each vehicle using its Webfleet object UID, then forward current object reports. Microdegree coordinates, GPS time, speed, course, ignition, odometer and engine-operation time are normalised for fleet maps, safety rules and usage-based maintenance.

Motive connector

Register each vehicle using its Motive vehicle ID, then forward vehicle-location responses. Metric and documented imperial speed and odometer values, engine hours, fuel, battery and movement state are normalised for live maps, safety alerts and maintenance schedules.

Powerfleet / Fleet Complete connector

Register each vehicle using its Powerfleet vehicle ID, then forward Unity getLatestSnapshots, getSnapshots, getActiveVehicles or getVehicles responses. Legacy Fleet Complete asset-position responses are supported when wrapped with their asset ID. Documented arc-minute coordinates, speed, direction, altitude, ignition, odometer and engine readings are normalised for fleet maps, geofences and maintenance.

Trackunit connector

Register each construction asset using its Trackunit asset UUID, then forward a single Location API GeoJSON feature or a paginated locations response. Longitude, latitude, optional altitude, accuracy, speed, heading, timestamp and address are normalised for live maps, trips, geofences and safety rules.

Verizon Connect connector

Register each vehicle using its exact Reveal vehicle number, then forward GPS webhook events or polling responses. Use a scoped company API key as a bearer token, or configure the Reveal GPS webhook with username prestartpilot and the same key as its password. Location, heading, ignition, odometer and engine-hour values feed the connected live fleet, geofences and maintenance workflows.

Digital Matter connector

Register each tracker using its Digital Matter serial number, then forward Device Manager HTTP/HTTPS JSON connector payloads or Telematics Guru telemetry responses. Device identity, GPS time, coordinates, speed, heading, altitude, accuracy, ignition inputs and diagnostics are normalised for the connected fleet view.

curl -X POST https://prestartpilot.com/api/v1/positions \
  -H "Authorization: Bearer psp_live_…" \
  -H "Content-Type: application/json" \
  -d '{"externalId":"device-014","recordedAt":"2026-08-03T11:00:00Z","latitude":-27.47,"longitude":153.02,"speedKph":28.4,"ignition":true}'