Use the John Deere Connection Management API (client_credentials grant) to audit and remove stale organization connections for a Connected Software application.
domain: developer.deere.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain an OAuth2 access token using the client_credentials grant type, since this API does not use the standard authorization_code user flow.
Call the Connection Management endpoint to list all organizations currently connected to your application, along with the granted permissions for each.
Inspect the permissions array returned for each connection to confirm the scopes still match what the integration needs.
Call the removal operation for a specific connection to revoke your application's access to an organization, including any related partner connections.
Re-verify connection state by re-listing connections after removal.
Known gotchas
This endpoint only works with a client_credentials token; using a user-authorized token will fail.
Removing a connection also removes any partner connections tied to it, which can be broader than expected.
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?