Skip to main content

List CRM fields

Read standard and organization-defined fields with usage flags, semantics, and value metadata.

GET/api/crm/fields
HTTP referenceScope leads:read for lead; companies:read for company; deals:read for deal; all three for omitted entity_typeUpdated September 27, 2026

This page documents the canonical HTTP contract for this endpoint.

This read is organization-specific: custom definitions are loaded for the authenticated organization. Standard fields are code-defined. Use the returned id and definition_id values rather than manufacturing custom-field identifiers.

Developer-key access is decided by the API authorization resolver: entity_type=lead requires leads:read, company requires companies:read, and deal requires deals:read. Omitting entity_type returns all three catalogs and requires all three read scopes.

The response example shows one representative standard field; actual responses may contain many standard and organization-defined fields. Each field carries flags, field_semantics/fieldSemantics, and value_schema/valueSchema where defined. The canonical shared definitions are available from field semantics and value schema. Usage filtering applies the returned capabilities; for example, bulk_update includes only fields whose bulk_update.supported is true.

Query parameters

  • entity_type · optional

    string

    lead, company, or deal. Omitted returns fields for all three.

  • usage · optional

    string

    Optional usage filter: profile, table, bulk_update, sync_to_leads, filter, sort, search, task_context, sequence_variables, or ai_context.

  • include_standard · optional

    boolean

    Include code-defined standard fields; defaults to true. Organization-defined custom fields remain organization-scoped.

Errors

StatusMeaning
401Authentication required or authenticated user has no organization context.
403Developer API key lacks the scope required for the selected entity_type.
422Invalid entity_type or usage value.

Docs