Operator platform

Build with order data users deliberately share.

Register your service, test against a synthetic sandbox, request narrowly scoped production access, and operate through mTLS with explicit per-resource consent.

The model

User control is the API contract.

01

Register

Describe the purpose, privacy terms, linking flow, requested scopes, and mandatory BOT attribution.

02

Prove

Use a locally generated private key and CSR, or download a short-lived one-time P12 package.

03

Sync

Pull only integration-specific resources selected by the user, with complete allowed history and revocation tombstones.

App experience

Users stay in control from discovery to connection.

Preview from the current app development build. The app-store versions with Integrations are not live yet, but operators can already build and validate their implementation in the sandbox.

Approved scopes only

Examples of data an integration can read

The API returns only fields approved for the integration and only for orders or existing vehicles the user explicitly selected.

  • Order and configuration model, variant, option_codes, colour, wheels, interior, Autopilot and tow hitch.
  • Delivery progress Country, delivery centre, order date, delivery-window text and dates, current status and milestone timestamps.
  • Shipping Vessel, voyage, loading and destination ports, estimated times and shipping events.
  • Complete allowed history Sequence, changed field, operation, previous and new value, event time, observation time and data quality.
  • Existing-vehicle telemetry Configuration, battery and range, charging state and power, mileage, software version, tyre pressure and option codes.
  • Anonymous statistics Country-level counts, timelines, distributions and lead-time percentiles when the user separately opts in.
Never included

VINs, real order numbers, BOT or Tesla account data, contact details, addresses, payment or financing data, access tokens, precise location and sensitive live security states.