API and integration guide

Know what is connected—and what is rehearsed.

GoAuto CRM separates tenant-scoped API access, inventory ingestion and vendor adapter rehearsals so connection claims can stay precise.

01

Use deliberate API access

The integration API supports scoped inventory reads, lead and customer operations, appointment creation and health access. Authorized managers control credentials and configured webhook events; credentials should receive only the access a reviewed use case needs.

02

Treat inventory sources individually

Website ingestion and configured refresh depend on the public source, supported extraction and deployment of a runner. Review diagnostics and reconciliation results before relying on a source operationally.

03

Read the rehearsal label

Inventory, lead, customer, DMS transfer, CRM migration and feed-publishing adapter contracts can be exercised with synthetic fixtures. These rehearsals do not verify provider acceptance, write to a live vendor or publish a real feed.

04

Discuss a live connection separately

A live integration needs a specific provider, account authorization, reviewed credentials, acceptance evidence and an operational owner. Lender and F&I integrations are not advertised as complete, and the public demo cannot activate external providers.

See the work come together

A clearer next step.
A more connected dealership.

Explore the workspace with synthetic data, or talk through your dealership’s needs.

Try the Live DemoLet’s talk