Retrieve contract record schema and list records via the Ironclad CLM API
domain: developer.ironcladapp.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Register an OAuth application in the Ironclad developer portal and request the public.records.readSchemas and public.records.readRecords scopes
Obtain an access token via the OAuth 2.0 client credentials or authorization code flow against the Ironclad token endpoint
Call GET /public/api/v1/records/metadata to retrieve the schema; the response includes a properties object mapping each record field key to its type (string, date, number, email, monetary_amount) — use this to understand which keys to filter on
List records with GET /public/api/v1/records, adding query parameters to filter by record type, date ranges, or field values; the response is paginated via a nextPageToken
Fetch a specific record with GET /public/api/v1/records/{recordId} to obtain all field values including counterparty name, effective date, expiry date, and attached document URLs
Map Ironclad field keys (from the schema endpoint) to your internal data model before storing or displaying records
Known gotchas
Schema keys are account-specific custom field names; never hardcode field names from one Ironclad environment — always fetch the schema dynamically in your integration
The records list endpoint is paginated; always follow nextPageToken until it is absent to retrieve the full dataset
Ironclad API base URL is na1.ironcladapp.com for North America accounts; confirm the correct regional base URL for your tenant before deploying
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?