Skip to main content
POST
Create a custom field
Custom fields allow you to define and organize additional attributes for your contacts beyond the standard fields (email, phone, name).

Use Cases

  • Lead qualification: Store lead score, source, or stage
  • Segmentation: Categorize contacts by industry, plan, or region
  • Personalization: Store preferences for personalized messaging
  • Integration sync: Map external CRM fields to Minimo

Field Types

Best Practices

Use SNAKE_CASE for keys (e.g., COMPANY_SIZE, LEAD_SOURCE). Keys are automatically uppercased.
Group related fields using categories like “Company Info”, “Lead Data”, “Preferences” for better organization.
Choose the right type for your data. Use number for numeric values, date for dates, and select for predefined options.

Common Errors

Code Examples

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Body

application/json
key
string
required

Unique identifier (will be uppercased)

Example:

"COMPANY_SIZE"

displayName
string
required

Human-readable label

Example:

"Company Size"

type
enum<string>
required

Field type

Available options:
text,
number,
boolean,
date,
datetime,
select,
json
Example:

"text"

category
string

Category for grouping fields

Example:

"Company Info"

acceptableValues
object

Acceptable values for select/enum types

metadata
object

Additional metadata

visibility
boolean
default:false

Whether field is visible in UI

Response

Custom field created successfully

data
object
Example: