kind equal to contacts, companies or opportunities:
GET /api/v1/crm/{kind}/fields: active field definitions, keys, types, options and required rules.GET /api/v1/crm/{kind}?page=1&pageSize=20: paginated records;querysearches fixed identity fields.GET /api/v1/crm/{kind}/{recordId}: one accessible record.POST /api/v1/crm/{kind}: fixed create fields plus optionalcustomFields.PATCH /api/v1/crm/{kind}/{recordId}: currentversion, changed fixed fields and acustomFieldspatch.
{"version": 3, "customFields": {"starter_location": "Hyderabad", "starter_budget": 8000000}} to patch an opportunity after reading its current version and field definitions. Use null to clear a custom value. Create/update returns the ID and version; read the record to get normalized values and customFieldDisplay labels. Opportunities must be enabled in Business profile. These endpoints do not send messages or create payments.
Use Filters to combine system and custom-field conditions with AND and OR on the web lists. Lead fields can also narrow follow-ups through their linked lead. Saved views retain the groups; a deleted or hidden field makes a stale group match no records until you edit or clear it.
Record links
Choose Record link to point to a lead, contact, company, opportunity or user. Choose one target type and either one record or multiple records when creating the field. These choices stay fixed; add another field to use a different target type or cardinality. Each owner type can have up to 10 record-link fields, including hidden fields. A multiple-record field holds up to 20 links. The field is offered after its database update is applied; until then existing fields keep working. Type a name, email or phone in the picker and choose an exact result. Users require the same HR visibility as their record page. Names open the linked record. Each viewer sees only targets they can currently access. Archived leads, disabled opportunities, removed users and deleted or inaccessible records show no linked name or detail and count as absent. Deleting a target removes its links and never requires clearing incoming links first. Archiving or disabling hides preserved links; restoring access makes surviving links visible again. The target page has Linked from, grouped by field name and limited to source records the viewer can see. More than 50 links use Previous and Next. Filters offer is, is not, is empty and is not empty; saved views keep these conditions. Lists and CSV exports use the same current visibility. CSV import on Leads accepts an exact name, email or phone belonging to the chosen target kind. Separate multiple entries with|. An unmatched or ambiguous entry rejects the
row with a reason; Marro never chooses between matching names. Opportunities match their own name.
Ask Marro or the staff WhatsApp agent to read links, find targets, show incoming links or replace
one field. Replacements name the source, field and selected records for approval and recheck
current access and names before saving. Text in a linked record cannot authorize another action.
For API writes, a record-link value is an array of numeric target IDs, even for a single-record
field; [] or null clears it. Definitions include recordLink.target and
recordLink.multiple. Reads return arrays of accessible {id, kind, name, href} objects.
Lead destinations require leads.read; contact/company/opportunity destinations require
crm.records.read. There is no public API scope for user destinations. Record links cannot be
anonymous website-form questions or captured through a lead-capture key.
The native app has no record-link editor or incoming-link screen. Its current lead-form contract
omits this unsupported type so older apps do not render it as a text input. Customer/opportunity
details show the safe, server-formatted names read-only. Use the web form or Ask Marro to edit links;
creating a record with a required link needs the web form or assistant. Optional links do not block
ordinary native forms. Native Ask Marro shares the server tools after the server release.
Background agents and automation Set fields do not gain automatic record-link writes. Use the web form, the scoped API or an approved assistant replacement. Anonymous website forms do not offer record links.