Manage architectural control (ACC) requests and reference data via the CINC Systems API
domain: cincapidocumentation.netlify.app · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Obtain a bearer token via the CINC Systems OAuth2 client credentials flow
Call GET https://yourcustomerdatabase.cincsys.com/api/management/{mgmtId}/associations/ACCInfo to list architectural requests, optionally filtered by assocCode
Call GET https://yourcustomerdatabase.cincsys.com/api/management/{mgmtId}/ACCType to retrieve valid ACC request type reference data
Use the corresponding POST on the ACCInfo endpoint to submit a new architectural request
Validate submitted request types against the ACCType reference list before posting
Known gotchas
ACCInfo and ACCType are separate endpoints; the type reference data is not embedded in the request payload, so fetch it separately to validate submissions
Only ACCInfo supports POST; ACCType is read-only reference data
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?