Field Types
To Start Off
Fields and their Field codes, Types, and Values
Fields follow the JSON format listed in the tables in the following sections:
Each field in a Kintone app has a Field Code, that is unique within the App. These field codes are necessary when creating, retrieving, and updating data via API. To check or change the field code, hover over the field in the App's settings, and open up the settings menu from the cog wheel that appears.
The field codes for the below fields cannot be changed - in this case, specify the name of these fields when using the Kintone API.
- Categories
- Status
- Assignee
Kintone has various fields that can be placed inside the App - the type specifies what type of field the target belongs to. The type will be responded back when retrieving Kintone data, but will not be needed when creating or updating data.
* There is an exception when creating/updating tables using the JavaScript API, where in some cases the TYPE will need to be specified.
The value specifies the value the field holds, or will hold, depending on what API used.
The Record number and the Record ID
These two fields sound alike, but make sure to understand the difference before moving on. However, if the App Code settings are not altered, these two fields hold the same values.
- Record Number
A Record Number is a number automatically given to each record of an App.
The number is unique within the App, meaning that no two records in the App can have the same Record Number.
However, the format of the Record Number can be altered through the advanced settings of the App, by specifying an App Code. If you specify your App Code to be "APPCODE", then your Record Number will be in the following sample format: "APPCODE-1". - Record ID
The Record ID, rather much like the Record Number, is a number automatically given to each record of an App. The Record ID will always be a number.
Use the Record ID when you are using Kintone APIs.
Field Responses
FIELD | TYPE | SAMPLE RESPONSE (Replace <field_code> with your field's field code) |
---|---|---|
Record number | RECORD_NUMBER | If an App Code is not set (default):"<field_code>": {If an App Code is set: "<field_code>": { |
Record ID | __ID__ | "$id": { |
Revision | __REVISION__ | "$revision": { |
Created by | CREATOR | For Kintone users:"<field_code>": {For guest users: "<field_code>": { |
Created datetime | CREATED_TIME | "<field_code>": {Reference: Date Formats |
Updated by | MODIFIER | For Kintone users:"<field_code>": {For guest users: "<field_code>": { |
Updated datetime | UPDATED_TIME | "<field_code>": {Reference: Date Formats |
Text | SINGLE_LINE_TEXT | "<field_code>": { |
Number | NUMBER | "<field_code>": { |
Calculated | CALC | "<field_code>": {The "value" will vary depending on the "Show as" option set on the field's settings
|
Text area | MULTI_LINE_TEXT | "<field_code>": { |
Rich text | RICH_TEXT | "<field_code>": { |
Check box | CHECK_BOX | "<field_code>": { |
Radio button | RADIO_BUTTON | "<field_code>": { |
Drop-down | DROP_DOWN | "<field_code>": { |
Multi-choice | MULTI_SELECT | "<field_code>": { |
Attachment | FILE | "<field_code>": {The fileKey included in the response can only be used for downloading files. |
Link | LINK | "<field_code>": { |
Date | DATE | "<field_code>": { |
Time | TIME | "<field_code>": { |
Date and time | DATETIME | "<field_code>": {Reference: Date Formats |
User selection | USER_SELECT | For Kintone users:"<field_code>": {For guest users: "<field_code>": { |
Department Selection | ORGANIZATION_SELECT | "<field_code>": { |
Group Selection | GROUP_SELECT | "<field_code>": { |
Categories | CATEGORY | "Categories": { |
Status | STATUS | "Status": { |
Assignee | STATUS_ASSIGNEE | "Assignee": { |
Lookup | SINGLE_LINE_TEXT or NUMBER *This depends on the field type of the Key Field. |
If the Key fields is a SINGLE_LINE_TEXT"<field_code>": {If the Key fields is a NUMBER "<field_code>": { |
Table | SUBTABLE | "<field_code>": { |
Field Requests
FIELD | TYPE | SAMPLE REQUEST (Replace <field_code> with your field's field code) |
---|---|---|
Record number | RECORD_NUMBER | Values for this field cannot be created or updated. |
Record ID | __ID__ | Values for this field cannot be created or updated. |
Revision | __REVISION__ | Values for this field cannot be created or updated. |
Created by | CREATOR | "<field_code>": {Values for this field cannot be updated. |
Created datetime | CREATED_TIME | "<field_code>": {or "<field_code>": {Values for this field cannot be updated. Future dates and times cannot be set. Reference: Date Formats |
Updated by | MODIFIER | "<field_code>": {Values for this field cannot be updated. |
Updated datetime | UPDATED_TIME | "<field_code>": {or "<field_code>": {Values for this field cannot be updated. Future dates and times cannot be set. Reference: Date Formats |
Text | SINGLE_LINE_TEXT | "<field_code>": { |
Number | NUMBER | "<field_code>": { |
Calculated | CALC | Values for this field cannot be created or updated. |
Text Area | MULTI_LINE_TEXT | "<field_code>": { |
Rich text | RICH_TEXT | "<field_code>": { |
Check box * | CHECK_BOX | "<field_code>": {Check box |
Radio button * | RADIO_BUTTON | "<field_code>": { |
Drop-down * | DROP_DOWN | "<field_code>": { |
Multi-choice * | MULTI_SELECT | "<field_code>": { |
Attachment | FILE | "<field_code>": { |
Link | LINK | "<field_code>": { |
Date | DATE | "<field_code>": { |
Time | TIME | "<field_code>": { |
Date and time | DATETIME | "<field_code>": {or "<field_code>": {Reference: Date Formats |
User selection | USER_SELECT | "<field_code>": { |
Department Selection | ORGANIZATION_SELECT | "<field_code>": { |
Group Selection | GROUP_SELECT | "<field_code>": { |
Categories | CATEGORY | Values for this field cannot be created or updated. |
Status | STATUS | Values for this field cannot be created or updated. |
Assignee | STATUS_ASSIGNEE | Values for this field cannot be created or updated. |
Lookup | SINGLE_LINE_TEXT or NUMBER *This depends on the field type of the Key Field. |
"<field_code>": {The "Prohibit duplicate values" option must be checked for the source App's key field. To use API tokens in Apps that contain Lookup fields, refer to the following article: API Tokens - Limitations |
Table | SUBTABLE | "<field_code>": {
|
*For the values, specify the options that you set up in the field's settings (deleted options can still be specified via API or CSV)
Empty Value Responses
Empty Values are responded in the following ways:
FIELD TYPE | RESPONDED EMPTY VALUE |
---|---|
|
When using JavaScript APIs on the Record Add page and the Record Edit page{ "value": undefined }When using JavaScript APIs on other pages, or when using REST APIs { "value": "" } |
|
When using JavaScript API or REST APIs{ "value": "" } |
|
When using JavaScript APIs on the Record Add page and the Record Edit page{ "value": undefined }When using JavaScript APIs on other pages, or when using REST APIs { "value": null } |
|
When using REST APIs{ "value": null }When using JavaScript APIs on the Record Add page and the Record Edit page { "value": undefined }When using JavaScript APIs on other pages { "value": "" } |
|
When using REST APIs{ "value": null }When using JavaScript APIs { "value": "" } |
|
When using JavaScript APIs or REST APIs{ "value": [] } |
Empty Value Requests
Empty Values are requested in the following ways:
FIELD TYPE | RESPONDED EMPTY VALUE |
---|---|
|
{ "value": "" }or { "value": null } |
|
"value": ""or "value": undefinedor "value": null |
|
{ "value": null } |
|
{ "value": [] } |
|
N/A |