Create and reference custom fields on Close CRM leads and contacts via API

domain: developer.close.com · 4 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

  1. Define a custom field schema against the appropriate object type endpoint: /custom_field_schema/{object_type}/ where object_type is one of lead, contact, opportunity, activity/<cat_id>, or custom_object/<cotype_id>.
  2. Note the field's generated ID after creation, since values are referenced using that ID rather than a human-readable name.
  3. When reading a record, custom field values appear as custom.FIELD_ID keys (e.g. custom.cf_v6S011I6MqcbVvB2FA5Nk8dr5MkL8sWuCiG8cUleO9c).
  4. To set a value, include the same custom.FIELD_ID key in the create/update payload for the lead, contact, or opportunity.

Known gotchas

Related routes

Use Close CRM's smart view search API to query leads with complex filter combinations, export matching lead IDs, and bulk-update a custom field across the result set
close.com · 5 steps · unrated
Import leads into Close CRM using the REST API
developer.close.com · 5 steps · unrated
Use Close CRM's bulk email sequence enrollment API to add a list of leads to a sequence, handle partial failures, and track sequence state via the activity feed
close.com · 5 steps · unrated

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?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans