PreStartPilot
Start free

PRACTICAL GUIDE

Integrations and API

Create scoped API keys, subscribe to webhooks and connect operational or telematics systems.

STEP 01

Create and revoke an API key

A scoped company key should be limited to the systems and data it actually needs.

  1. 1

    Open Integrations, name the connection and select the required read or write permissions.

  2. 2

    Create the key and copy it immediately into the destination secret manager; it is not shown again.

  3. 3

    Revoke the key when the integration is retired, exposed or transferred to a different owner.

STEP 02

Configure a secure webhook

Webhooks send selected company events to an HTTPS endpoint with a signing secret.

  1. 1

    Create an HTTPS receiver that can verify the PreStartPilot signature before processing the body.

  2. 2

    Register the endpoint, choose the required event types and store the generated secret securely.

  3. 3

    Test delivery, handle duplicate events idempotently and monitor retries or failures in PreStartPilot.

STEP 03

Send GPS positions to PreStartPilot

Position payloads are authenticated and matched to a registered company device identifier.

  1. 1

    Register the tracker in GPS Tracking and record the exact external device identifier.

  2. 2

    Configure the provider or gateway to send supported position data to the company integration endpoint with its API key.

  3. 3

    Verify the device timestamp and location on the live map, then test route history and a geofence crossing.

STEP 04

Download a controlled integration pack

Accounting, project-delivery and reporting-warehouse ZIP packs work without third-party credentials or an external connection.

  1. 1

    Open Company & API, find the Integration marketplace and choose the pack that matches the handoff.

  2. 2

    Download the ZIP and review README.txt plus manifest.json before opening or importing its tenant-scoped CSV files.

  3. 3

    Confirm field mapping, payroll, tax, accounting and project-control rules with the responsible person before importing; the export does not send data to a provider.

STEP 05

Understand provider connection status

A marketplace tile describes a foundation, not proof that a third-party account is connected.

  1. 1

    Use Ready now packs immediately; they require no third-party credentials and create an audit receipt.

  2. 2

    Use Configure tiles for the PreStartPilot API or signed webhooks after creating a least-privilege key or verified receiver.

  3. 3

    Treat Provider credentials required tiles as unavailable until the provider app registration, credentials, customer authorisation and field mapping have been reviewed and configured.

STEP 06

Connect an environmental sensor

Environmental gateways send bounded readings through a dedicated company permission; provider credentials are not implied or required by PreStartPilot.

  1. 1

    Open Environmental monitoring, add the device, choose its site and define the exact metric, unit, warning limit and critical limit used by the calibrated instrument.

  2. 2

    Open Company & API and create a least-privilege key with sensors:write only, then store it in the gateway secret manager and send one to 100 recent readings to /api/v1/environmental-readings.

  3. 3

    Confirm the device signal time and threshold status in Environmental monitoring, test a controlled threshold crossing and normal recovery, then revoke the key if the gateway is retired or exposed.