
API Documentation
Endpoints, schemas, error handling and version policy.
Reference · v1 · reviewed 1 Oct 2026
Open API Documentation
Global Automotive Commerce
Developer Hub
Explore integration topics, review access requirements and find the right technical reference for your use case.
// 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
The Developer Hub routes you to the owners of each area. Detailed endpoints and event catalogs live on their own pages.

Endpoints, schemas, error handling and version policy.
Reference · v1 · reviewed 1 Oct 2026
Open API Documentation
Event topics, signature verification and delivery semantics.
Reference · Event spec v1 · reviewed 1 Oct 2026
Open Webhooks
Catalog, stock and feed mappings with provenance and reconciliation.
Guide · Reviewed 28 Sep 2026
Open Inventory & Catalog Integrations
Supported order and service-booking flows with reconciliation rules.
Guide · Pilot · reviewed 25 Sep 2026
Open Order & Booking Integrations
Current and historical component status from an authoritative source.
Operational · Live source
Open Platform Status
Authentication, scopes, secret handling and incident process.
Guidance · Reviewed 30 Sep 2026
Open Security & Integration GuidanceUse cases
Choose a use case to see where its maintained reference lives. Only source-backed options are shown as supported.

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

Readable without signing in.
Some content needs a verified organization and approved access.
Limited to approved participants; scope may change.
Not offered for this market or organization.
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”.
Search
Results respect access before anything is shown — restricted titles, snippets and counts never appear unless you're entitled.
Integration readiness
Checklist — nothing is saved or scored
0 of 6 ready

You tell us what you want to build.
Your organization and role are confirmed.
Least-privilege scopes reviewed by approvers.
Synthetic fixtures only — no live customer data.
Separate product, security and operational approval.
Request access
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.

Security & privacy


Found a documentation error or a security concern? Report it — don't include secrets or personal data.
Read security & integration guidanceFAQ
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.