Skip to main content
When you fetch the board schema, each field includes a type property. This type determines what value format the API expects when you create or update a card. Always fetch the schema before writing to a board so you know the key and type for each field.

Field types

text

A plain text string.

number

A numeric value. Do not wrap in quotes.

money

A numeric value representing a dollar amount. Do not include currency symbols or commas.

date

An ISO 8601 date string.

datetime

An ISO 8601 datetime string with timezone.

boolean

true or false.

select

A single string value matching one of the field’s configured options exactly. Option values are case-sensitive.

multiselect

An array of strings, each matching a configured option exactly.

person

A single contact ID string referencing a contact in your company.

persons

An array of contact ID strings.

email

A valid email address string.

phone

A phone number string. Include country code for best compatibility.

url

A fully qualified URL string.

file

Files are attached via the Upload a file to a card endpoint, not via field keys in the card body.

Reading field values

When you fetch a card, field values are returned using the same key/value structure. Null or unset fields are returned as null.

Unknown types

If the schema returns a type not listed here, treat the value as a plain string and contact Aptly support to confirm the expected format.