Crelate API: authenticate with an API key and create or update a record
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 view/enable your personal API key (an org admin must first enable API access for non-admin users under Settings > Advanced Settings > User Roles).
Append the key as a query-string parameter on every request, e.g. https://app.crelate.com/api3/{resource}/{id}?api_key={key}.
To create or update a record, send the entity fields as JSON, supplying required attributes for that type (e.g. Company requires Name; Job requires Name; Note and Task require Body).
For lookup fields (suffixed _Id, e.g. AdditionalContact_Billing_Id), either pass the related record's Id to attach an existing record, or leave Id blank and supply FirstName/LastName to have Crelate create a new linked contact.
Send all dates in ISO 8601 UTC format (e.g. 2017-01-01T15:00:00Z); other formats or time zones can fail or produce unpredictable results.
Use the published Swagger definition (https://app.crelate.com/api3/swagger/v3/swagger.json) to confirm the exact field set and generate a typed client if needed.
Known gotchas
Passing the API key as a URL query-string parameter means it can end up in server/proxy logs — treat it as sensitive and rotate it if exposed.
Missing a required attribute (Company.Name, Job.Name, Note.Body, Task.Body) returns an HTTP 500 with the missing fields listed in the body, not a 4xx validation error.
Tags must be nested under a Tags object keyed by your organization's tag category names (using 'Default' for the default category) — a flat tags array is not accepted.
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?