Register as a developer on the Fortellis platform (fortellis.io) and create an application subscribing to the relevant inventory async API topic in the Fortellis API directory
List your application in the Fortellis marketplace so that dealerships can discover and authorize your application; each dealership authorization grants your app access to their inventory feed
Configure your event consumer to connect to the Fortellis async API delivery mechanism, which is based on a publish-subscribe model; retrieve your endpoint or subscription configuration from the Fortellis developer console
Consume incoming inventory events that represent vehicle adds, updates, and removals in the dealer's DMS, parsing the event payload for VIN, stock number, year, make, model, trim, price, and status fields
Apply idempotent upsert logic keyed on VIN and dealer ID to maintain an accurate current-state inventory snapshot, handling out-of-order event delivery
Use the Fortellis DevCare Portal (introduced at NADA 2026) to monitor event delivery health, investigate delivery failures, and manage API subscriptions across dealer installations
Known gotchas
Async API events are dealer-specific and authorization-gated; your application will only receive events for dealerships that have explicitly installed and authorized your Fortellis marketplace listing
Fortellis async APIs are event-driven and do not guarantee strict ordering; your consumer must handle late-arriving or duplicated events using idempotency rather than assuming sequential delivery
The Fortellis marketplace approval process requires adherence to CDK's API partner policies and may include a review period; plan for this when scoping your dealer connectivity timeline
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp