Create a developer account at developer.fortellis.io and register your application in the Fortellis Developer Network.
Browse the Fortellis API Directory at apidocs.fortellis.io to find the CDK-published APIs relevant to your use case (service repair orders, parts inventory, vehicle sales, CRM).
Subscribe to the desired API in the marketplace; each API subscription requires dealer authorization — the subscribing dealership must also activate the integration in the Fortellis Marketplace portal.
Use the OAuth 2.0 client credentials flow to obtain a Fortellis platform access token by posting to the Fortellis authorization server with your application's client credentials.
Make API calls by including the access token as a Bearer token and including the required dealer-context headers (such as the dealership identifier) as specified in each API's documentation.
For high-volume or event-driven use cases, use the CDK Async APIs available through Fortellis, which deliver data via webhooks rather than synchronous request-response.
Known gotchas
Fortellis APIs are not directly accessible by developers alone; each dealer must independently subscribe to and authorize your application in the marketplace before you receive dealer-scoped data, making automated mass onboarding impossible.
CDK Global DMS integration depth and available API surface vary by dealership's CDK product tier (CDK Drive vs. CDK CRM vs. others); verify which APIs your target dealers have access to before designing your data model.
The CDK Modern API platform introduced breaking changes from legacy integration patterns; if working with dealers who have older CDK integrations, consult the CDK Modern APIs Migration Guide published on the Fortellis community.
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