Authenticate to CINC Systems' community association API using OAuth2 client credentials
domain: cincapidocumentation.netlify.app · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Request a Client ID and Client Secret from CINC Systems for your integration
POST the Client ID and Client Secret to https://identity.cincsys.com/connect/token to obtain a bearer token
Optionally pass a scope parameter; if omitted, the default scope is 'All'
Attach the returned bearer token to subsequent calls against your tenant's https://yourcustomerdatabase.cincsys.com/api/management/{mgmtId}/... endpoints
Use the returned refresh token to renew the bearer token before its 60-minute expiry, rather than re-running the full Client ID/Client Secret exchange each time
Known gotchas
The bearer token expires 60 minutes after issuance, but CINC's own Setup and Authentication docs confirm a refresh token can be obtained alongside it - build proactive refresh-token renewal rather than assuming re-authentication is the only option
The API base host is tenant-specific (yourcustomerdatabase.cincsys.com is a placeholder), so hardcoding a shared hostname across customers will fail
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?