Authenticate to Crelate's REST API and read/write contacts and jobs
domain: crelate.com · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
In Crelate, go to Settings > My Settings & Preferences to find your API Key (org admins have it by default; non-admins need an admin to enable API Access under Settings > Advanced Settings > User Roles > Misc).
Copy the generated API key; regenerating the key or disabling API access immediately breaks any existing integrations using the old key.
Make requests against base https://app.crelate.com/api3/, passing the key as a querystring parameter, e.g. https://app.crelate.com/api3/contacts/{contactId}?api_key={key}.
For lookup/reference fields, use the *_Id / *_FirstName / *_LastName field triplet convention: supplying the _Id attaches an existing record and Crelate ignores the name fields; leaving _Id blank with FirstName/LastName populated auto-creates a new linked record.
Supply required fields per entity type — Crelate enforces Company: Name, Job: Name, Note: Body, and Task: Body; omitting them returns HTTP 500 with the list of missing fields in the response body.
For discovery/codegen, pull the OpenAPI/Swagger definition at https://app.crelate.com/api3/swagger/v3/swagger.json and browse the interactive reference at https://app.crelate.com/api3/docs.
Known gotchas
All date/time values must be ISO 8601 in UTC (e.g. '2017-01-01T15:00:00Z') — any other format or timezone can fail the request or produce unpredictable results, per Crelate's own docs.
The API key travels in the URL querystring, not a header — unusual among modern REST APIs and a risk for keys leaking into server/proxy logs.
API access is off by default for non-admin users and must be explicitly enabled per-org and then per-user before any key will work.
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?