Global Automotive Commerce

Preparing your experience0%

Developer Hub

Build integrations with clear documentation.

Explore integration topics, review access requirements and find the right technical reference for your use case.

example.pseudo
// Pseudocode — see API Documentation for real contracts
request  = build_request(resource: "listings",
                         version: "check current docs")
response = send(request, auth: YOUR_APPROVED_CREDENTIAL)

if response.status is error:
    log(response.request_id)   // never log secrets
    retry_with_backoff()

Integration routes

Find the right technical reference

The Developer Hub routes you to the owners of each area. Detailed endpoints and event catalogs live on their own pages.

A person writing on printed documentation
Public

API Documentation

Endpoints, schemas, error handling and version policy.

Reference · v1 · reviewed 1 Oct 2026

Open API Documentation
Glass office towers against a blue sky
Partner access required

Webhooks

Event topics, signature verification and delivery semantics.

Reference · Event spec v1 · reviewed 1 Oct 2026

Open Webhooks
A person leaning against a classic car in a workshop
Pilot

Order & Booking Integrations

Supported order and service-booking flows with reconciliation rules.

Guide · Pilot · reviewed 25 Sep 2026

Open Order & Booking Integrations
Printed reports with charts next to a laptop
Public

Platform Status

Current and historical component status from an authoritative source.

Operational · Live source

Open Platform Status
A phone and paperwork on a desk
Partner access required

Security & Integration Guidance

Authentication, scopes, secret handling and incident process.

Guidance · Reviewed 30 Sep 2026

Open Security & Integration Guidance

Use cases

What are you trying to build?

Choose a use case to see where its maintained reference lives. Only source-backed options are shown as supported.

  1. 1UnderstandRead the public overview
  2. 2Select a routeOpen the specialist reference
  3. 3Review requirementsCheck access level and market
  4. 4Request accessOnly where a real review exists
A team discussing a plan on a screen in an open-plan office

Access levels

What each label means

Labels come from maintained access-policy records. We never show something as available by visual optimism.

A team gathered in an office for a briefing
Public

Readable without signing in.

Partner access required

Some content needs a verified organization and approved access.

Pilot

Limited to approved participants; scope may change.

Unavailable

Not offered for this market or organization.

Unknown

Availability is not confirmed for this market or organization.

Version and review dates

Each reference shows its version and last review. When unknown: “Check current documentation”.

Integration readiness

Before you request access

Checklist — nothing is saved or scored

0 of 6 ready

Two colleagues celebrating at a desk with a laptop
  1. 1

    Interest

    You tell us what you want to build.

  2. 2

    Organization verification

    Your organization and role are confirmed.

  3. 3

    Scoped access

    Least-privilege scopes reviewed by approvers.

  4. 4

    Testing

    Synthetic fixtures only — no live customer data.

  5. 5

    Production

    Separate product, security and operational approval.

Request access

Request technical access review

Tell us what you need. We'll record your request and route it to the right owner. There's no promise of issuance or approval time.

Printed reports and a laptop on a desk

Describe the data flow. No keys, tokens or personal data.

Security & privacy

Built around least privilege

A phone and paperwork on a desk

Credentials and secrets

  • Secrets are never shown in public pages, URLs or logs
  • Scopes are requested and approved individually
  • Credentials can be revoked with an audit record

FAQ

Developer Hub questions

Technical examples are illustrative unless an official versioned reference states otherwise.

It is a starting point for understanding available integration topics, locating maintained technical references and seeing the requirements for requesting appropriate access. It is not itself proof that a particular API or connector is live.

Yes, for anything labelled Public. Partner and pilot content needs a verified organization and approved access.

Open API Documentation from the integration routes above, or search the public documentation.

The Webhooks reference covers event topics, signature verification and delivery semantics. Some of it needs partner access.

Inventory & Catalog Integrations explains supported feed formats, mappings and reconciliation.

Order and booking flows are in pilot. Scope is limited to approved participants and may change.

Platform Status shows current and historical component status from an authoritative source.

No. Credentials are only issued after your organization is verified and the scopes you need are approved.

Testing uses synthetic fixtures only. Availability depends on your capability and market — check current documentation.

Only SDKs listed in the API Documentation are supported. Anything else should be treated as unofficial.

Use the request form on this page. It records your request and routes it to the right owner — there's no promise of approval time.

No. Availability is labelled per market and organization. Unknown means it isn't confirmed yet.

Store them in a secrets manager, never in code, URLs or logs, and request only the scopes you need.

Use Report a problem in the Security & privacy section. Don't include secrets or personal data.

Breaking changes come with a new version and a deprecation notice. Each reference shows its version and last review date.

No. Platform Status covers DriverXtra components, not your own systems or network.

No. Access is scoped to your own verified organization.

No. A request starts a technical review. Any commercial terms are agreed separately.

Integrating as a dealer or fleet?

See the business solutions that use these integrations.