Fields are custom built data points that allow customers to capture unique and custom data.
Listing Fields
Returns a collection of field records, optionally filtered by the available request parameters.
GET /api/v1/fields
Available Request Parameters:
| Name | Type | Required | Description |
| id | integer | no | ID of the field. |
| name | string | no | Name of the field. |
| field_type | integer | no | ID of the field type. |
| field_type_tag | string | no | Unique string reference for the field type. |
Available Field Types
| Field Type Name | Field Type Tag | Data Type | Description |
| Address | ADDRESS | json string | Address related properties |
| Country | COUNTRY | string | 2-character ISO country code. |
| Date | DATE | date | ISO formated date |
| Date (Birthday) | BIRTHDAY | date | ISO formatted date |
| Email Address | string | Valid email address | |
| Input (Long) | LONG | string | Multi-line string |
| Input (Short) | INPUT | string | Single line string |
| Money | CURRENCY | decimal | Numeric value |
| Multiple Choice (Checkbox) | CHECKBOX | json string | One or more valid choices |
| Multiple Choice (Dropdown) | SELECT | string | Valid choice |
| Multiple Choice (Radio) | RADIO | string | Valid choice |
| Name (First, Middle, Last) | NAME | json string | Name related properties |
| Number | NUMBER | decimal | Numeric value |
| Website (URL) | LINK | string | Valid website address |
| Yes or No | YESNO | boolean | 1 or 0 |
| Yes, No, or N/A | YESNONA | boolean | 1, 0, or an empty string |
Getting a Field
Returns a single case region record, based on the numeric ID.
GET /api/v1/fields/{field_id}
Formatting Field Values from API Endpoints
When retrieving field values from applicable API endpoints, custom field values will always be formatted as a string, boolean, or numeric value. If you would prefer to receive structured data on field types that support it, pass the expand_field_values parameter with a value of "1" to the query string and the result will include json objects or arrays where applicable.
Custom Field Reference
Please note, the IDs listed in these examples are for demonstration purposes. The ID's of your fields will change.
| Field Type | Description | Example Value |
| Address | A physical address |
{
|
| Country | A two character ISO country code |
{
|
| Date |
An ISO-formatted date stamp. The system can auto-detect some common date formats, however it is recommended to convert your dates into ISO format for consistency. |
{
|
| Input (Long Answer) |
A multi-line string. Line breaks can be added by using \n characters. |
{
|
| Input (Short Answer) | A single-line string. |
{
|
| Money | A numeric value (without currency code). |
{
|
| Multiple Choice |
An exact match from the available choices. Please review the available to choices for your multiple choice fields in order to properly validate the input before submitting the request. |
{
|
| Multiple Choice (Checkboxes) |
One or more matches from the available choices. Please review the available to choices for your multiple choice fields in order to properly validate the input before submitting the request. |
{
|
| Name |
A person's name. Only the last name is required. |
{
|
| Number |
A numeric value. Whole numbers and decimals are allowed. |
{
|
| Section |
A special field, used to provide a header or separator when displaying content on the screen. Read How to Create Custom Fields to see practical uses for section fields. |
{
|
| Website |
A fully qualified domain name. All website addresses must begin with https:// to be considered valid. |
{
|
| Yes / No |
A boolean value. Available choices are 1 or 0. |
{
|
| Yes / No / NA |
A boolean value with empty fields. Available choices are 1, 0, or an empty string. |
{
|