---
title: "Add Custom Field"
method: POST
path: "/v1.0/teamFeatures/custom-field"
tags: ["Team Features"]
---

# Add Custom Field

`POST /v1.0/teamFeatures/custom-field`

Creates a new lead-level custom field on the caller's team.

Notes:
- attributeName is required and is trimmed; empty names are rejected.
- attributeType is required. Supported types: text, number, date, anniversary_date, single_select, multi_select, percentage, currency.
  - anniversary_date: a date field that recurs annually (e.g. birthdays, work anniversaries). Accepts the same date format as date.
- The response body is a plain string message.

## Headers

- `Authorization` string, required
- `Content-Type` string, required

## Request body

- CustomAttribute — User customized field
  - `attributeName` string, required — The name of this custom field
  - `attributeType` string, required — The type of the field
  - `value` string, required — The content of the field for lead, value for multi-select,such as "[\"item1\",\"item2\s",...]" .It's unnecessary when adding a new custom field for team
  - `params` string — options for select, such as {"option":["item1","item2",...]}

## Response `200`

Custom field created.

- string

## Other responses

- `400` — attributeName empty (ATTRIBUTE_NAME_EMPTY) or attributeType empty (ATTRIBUTE_TYPE_EMPTY).
- `401` — Missing or invalid authentication token.
- `500` — Internal server error.

---

[API](https://skmtc.net/lofty/apis/lofty-service-open-apis.md) · [All operations](https://skmtc.net/lofty/apis/lofty-service-open-apis/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/lofty/lofty-service-open-apis/versions/23e640467118/schema)