Entity fields¶

API path: /entity/fields.

Fields actions¶

Field allows to add custom information to a customizable entity. Each field belongs to one entity.

field is:

<field> = {
    "id": 131312, //identifier, null when new object
    "label": "Additional info", 
    "type":  "text", //type of field, see below    
    "required": false, //whether field is required to be filled or not
    "description": "Info about place", //Additional info about the field, max 250 characters
    "params": { ... } //type-specific. If no specific params, this field should be omitted 
}

field types:

• text - text field up to 700 unicode symbols

Special params: none

• bigtext - bigger text field, up to 20000 unicode symbols with reduced search and sorting capabilities

Special params: none

• email - field for storing email, validated to contain valid email address

Special params: none

• phone - field for storing phone number, validated to contain valid phone number

Special params: none

• decimal - decimal number from -999999999999.999999 to 999999999999.999999 . Values are stored up to the sixth decimal place

Special params: none

• integer - integer number from -2^63 to 2^63 - 1

Special params: none

• employee - link to employee

Special params:

{
  "responsible": true //entities with this set to "true" can be shown to the employee in the mobile app.
                    //Only one employee field can have this value set to "true" 
}

• file - link to file

Special params:

{
  "allowed_extensions": ["docx", "pdf"]
}

• image - link to image file

Special params: none

read(entity_id)¶

Get a set of custom fields associated with the specified entity. Note that you must know entity id, which can be obtained from entity/list.

parameters¶

response¶

{
    "success": true,
    "list": [ <field>, ... ]
}

errors¶

• 201 (Not found in database) – if there is no entity with such ID

update(entity_id, fields, delete_missing)¶

Update a set of custom fields associated with the specified entity.

required subuser rights: places_custom_fields_update for fields associated with place entity

Fields passed with id equal to null will be created. If field already exists, its type must be equal to type of already stored field (i. e. you cannot change type of a field).

All fields associated with the same entity must have different labels.

Passing fields with id from non-existent fields or fields bound to another entity will result in an error.

WARNING If delete_missing is true, all existing fields which are missing from the fields list will be permanently deleted! Otherwise they are unaffected.

parameters¶

errors¶

• 201 (Not found in database) – if there is no entity with such ID
• 7 (Invalid parameters) - if fields violate restrictions described above

response¶

A list of all fields associated with the specified entity. Newly created fields will have their IDs filled.

{
    "success": true,
    "list": [ <field>, ... ]
}