Authenticate to the Fortellis Marketplace using the OAuth 2.0 Client Credentials flow and subscribe to a dealer DMS event feed
domain: fortellis.io · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Create a Fortellis API/app project in the developer portal and retrieve its API Key and API Secret from the project details page
Base64-encode 'API_KEY:API_SECRET' to form a Basic auth token, then POST it to the Fortellis identity token endpoint to mint a Bearer access token valid for one hour
Submit a Marketplace Listing for your app (public or private) so dealers/DMS providers can approve a subscription to your integration
Once a subscription is approved, use the Bearer token to call the DMS provider's event-feed API, including any subscription/customer identifier required by that specific API
Implement token refresh logic that re-mints a new Bearer token before the one-hour expiry rather than waiting for a 401 to trigger re-authentication
Known gotchas
The one-hour token lifetime is short for long-running batch jobs; build refresh into the client itself rather than assuming a single token lasts a full sync cycle
A Private marketplace listing requires an explicit dealer/DMS-provider invitation before your client credentials will be authorized to pull that customer's data, even if the OAuth token mint succeeds
Each underlying DMS API on Fortellis (sales, service, parts, etc.) has its own data contract and rate limits despite sharing the same identity/token layer, so don't assume uniform behavior across APIs just because auth is centralized
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?