API

GET /v1/zcrm/customers/<c_id>

Restores client by ID.

Address parameters

• c_id — client identification

Response

{
  "id": 65,
  "name": "Good company",
  "status": "company",
  "type": "client",
  "responsible_user_id": 20,
  "employees_count": "50",
  "comment": "",
  "country": "GB",
  "city": "London",
  "address": "",
  "zip": "",
  "website": "",
  "created_at": "2020-04-28 05:47:47",
  "created_by": 20,
  "lead_source": "manual",
  "lead_created_at": null,
  "lead_created_by": null,
  "phones": [
    {
      "type": "work",
      "phone": "+44123456789"
    }
  ],
  "contacts": [
    {
      "type": "email_work",
      "value": "good_company@example.com"
    }
  ],
  "labels": [
    {
      "id": 12,
      "label": "Best clients"
    }
  ],
  "custom_properties": [
    {
      "id": 18,
      "key": "loyalty",
      "title": "Loyalty",
      "value": "high"
    }
  ]
}

where:

• id — client identification
• name — client name
• status — client status. Possible values:
  • individual — personal user
  • company — company/business
• type — client type. Possible values:
  • potential — potential client
  • client — client
  • reseller — reseller
  • partner — partner
• responsible_user_id — responsible (user identification)
• employees_count — number of employees. Possible values:
  • 50 — less than 50
  • 50_250 — 50 – 250
  • 250_500 — 250 – 500
• comment — client description
• country — client country. Two-letter code (UK, US etc.)
• city — client city
• address — client address
• zip — zip code
• website — client website
• created_at — client creation date and time (format `YYYY-MM-DD HH:mm:ss`)
• created_by — created by (user identification)
• lead_source — source. Possible values:
  • manual — manual
  • call_incoming — incoming call
  • call_outgoing — outgoing call
  • form — form
• lead_created_at — lead creation date and time, if the client was created from a lead (format `YYYY-MM-DD HH:mm:ss`)
• lead_created_by — lead created by, if the client was created from a lead (user identification)
• phones — client phone numbers array. Each number contains the following fields:
  • type — number type. Possible values:
    • work — work
    • personal — personal
  • phone — phone number
• contacts — client contacts array. Each contact contains the following fields:
  • type — client type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value
• labels — tags/labels array, assigned to a client. Each label contains the following fields:
  • id — label identification
  • label — label value
• custom_properties — additional features array. Each additional feature contains the following fields:
  • id — additional feature identification
  • key — additional feature unique name
  • title — additional feature displayed name
  • value — additional feature value

POST /v1/zcrm/customers

Creates a new client with indicated data.

• customer — new client information. Client structure:

Parameters

{
    "name": "Good company",
    "status": "company",
    "type": "client",
    "responsible_user_id": 20,
    "employees_count": "50",
    "comment": "",
    "country": "GB",
    "city": "London",
    "address": "",
    "zip": "",
    "website": "",
    "lead_source": "manual",
    "phones": [
      {
        "type": "work",
        "phone": "+44123456789"
      }
    ],
    "contacts": [
      {
        "type": "email_work",
        "value": "good_company@example.com"
      }
    ],
    "labels": [
      { "id": 12 },
      { "id": 13 }
  ],
    "custom_properties": [
    {
        "id": 18,
        "value": "high"
      }
    ]
}

where:

• name — client name
• status — client status. Possible values:
  • individual — personal user
  • company — company/business
• type — client type. Possible values:
  • potential — potential client
  • client — client
  • reseller — reseller
  • partner — partner
• responsible_user_id — responsible (user identification)
• employees_count — number of employees. Possible values:
  • 50 — less than 50
  • 50_250 — 50 – 250
  • 250_500 — 250 – 500
• comment — client description
• country — client country. Two-letter code (UK, US etc.)
• city — client city
• address — client address
• zip — zip code
• website — client website
• lead_source — source. Possible values:
  • manual — вручную
  • call_incoming — incoming call
  • call_outgoing — outgoing call
  • form — form
• phones — phone numbers array. Each number contains the following fields:
  • type — number type. Possible values:
    • work — work
    • personal — personal
  • phone — number value
• contacts — client contacts array. Each contact contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value
• labels — tags/labels array, assigned to a client. Each label contains the following fields:
  • id — existing label identification
• custom_properties — additional features array. Each element must contain:
  • id — additional feature identification:
  • key — additional feature unique name
  • value — additional feature value

Response:

{
"id": 65
}

where:

• id — created client identification

PUT /v1/zcrm/customers/<c_id>

Updates an existing client with indicated ID.

Address parameters

• c_id — client identification

Parameters

• customer — new client data. Client structure:

{
    "name": "Good company",
    "status": "company",
    "type": "client",
    "responsible_user_id": 20,
    "employees_count": "50",
    "comment": "",
    "country": "GB",
    "city": "London",
    "address": "",
    "zip": "",
    "website": "",
    "lead_source": "manual",
    "phones": [
      {
        "type": "work",
        "phone": "+44123456789"
      }
    ],
    "contacts": [
      {
        "type": "email_work",
        "value": "good_company@example.com"
      }
    ],
    "labels": [
      { "id": 12 },
      { "id": 13 }
  ],
    "custom_properties": [
    {
        "id": 18,
        "value": "high"
      }
    ]
}

where:

• name — client name
• status — client status. Possible values:
  • individual — personal user
  • company — company/business
• type — client type. Possible values:
  • potential — potential client
  • client — client
  • reseller — reseller
  • partner — partner
• responsible_user_id — responsible (user identification)
• employees_count — number of employees. Possible values:
  • 50 — less than 50
  • 50_250 — 50 – 250
  • 250_500 — 250 – 500
• comment — client description
• country — client country. Two-letter code (UK, US etc.)
• city — client city
• address — client address
• zip — zip code
• website — client website
• created_at — client creation date and time (format YYYY-MM-DD HH:mm:ss)
• created_by — created by (user identification)
• lead_source — source. Possible values:
  • manual — manual
  • call_incoming — incoming call
  • call_outgoing — outgoing call
  • form — form
• phones — phone number array. Each number must contain the following fields:
  • type — number type. Possible values:
    • work — work
    • personal — personal
  • phone — phone number value
• contacts — client contacts array. Each contact contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value
• labels — tags/labels array, assigned to a client. Each label contains the following fields:
  • id — label identification
  • label — label value

DELETE /v1/zcrm/customers/<c_id>

Deleted a client by its ID.

Address parameters

• c_id — client identification

GET /v1/zcrm/customers/labels

Restores the list of all labels and their statistics.

Response

{
  "totalCount": 5,
  "labels": [
    {
      "id": 12,
      "label": "Best clients",
      "count": 14
    }
  ]
}

where:

• totalCount — total number of labels in the system
• labels — labels array. Each label has the following fields:
  • id — label identification
  • label — label name
  • count — number of clients and leads using this label

POST /v1/zcrm/customers/labels

Creates new label.

Parameters

• name — new label name

Response

{
  "id": 13,
  "label": "Best clients",
  "count": 0
}

where:

• id — created label identification
• label — label name
• count — number of clients and leads using this label (here always equals 0)

DELETE /v1/zcrm/customers/labels/<l_id>

Deletes label from the system using its ID.

Address parameters

• l_id — label identification

GET /v1/zcrm/customers/custom-properties

Restores additional features.

Response

{
  "totalCount": 8,
  "customProperties": [
    {
      "id": 18,
      "key": "loyalty",
      "title": "Loyalty"
    }
  ]
}

where:

• totalCount — total number of additional features.
• customProperties — array of additional features. Each additional feature includes the following fields:
  • id — additional feature identification
  • key — additional feature unique name
  • title — additional feature displayed name

GET /v1/zcrm/customers/<c_id>/feed

Restores records in client timeline.

Address parameters

• c_id — client identification

Response

{
  "totalCount": 17,
  "items": [
    {
      "id": 37825,
      "type": "note",
      "content": "Call to client",
      "time": "2020-06-08 06:55:02",
      "user_id": 20,
      "user_name": "John Smith",
      "call_id": null,
      "call_type": null,
      "call_status": null,
      "call_phone": null,
      "call_duration": null,
      "call_record": null,
      "call_contact_name": null,
      "attached_files": [
        {
          "file_id": 576,
          "original_filename": "filename.doc"
        }
      ]
    }
  ]
}

where:

• totalCount — total number of records
• items — records array. Each record contains the following attributes:
  • id — records identification
  • type — record type. Possible values:
    • event — event
    • note — text note
    • call — call
  • content — content. If record type is note, this attribute contains note text. If record type is event, this attribute contains event identification, for example:
    • CUSTOMER_CREATED — client creation event
    • LEAD_CREATED — lead creation event
  • time — record time in format `YYYY-MM-DD hh:mm:ss`
  • user_id — user identification, who created the record
  • user_name — user name, who created the record
  • call_id — call identification (if record type is call)
  • call_type — call type. Possible values:
    • incoming — incoming call
    • outgoing — outgoing call
  • call_status — call status. Possible values:
    • answer — successful call
    • noanswer — no answer
    • cancel — canceled
    • busy — busy
    • failed — failed call
  • call_phone — call phone number
  • call_duration — call duration in seconds
  • call_record — if call recording is enabled
  • call_contact_name — call contact name
  • attached_files — array of files attached to a note (if record type is a note). Each array element contains the following attributes:
    • file_id — file identification
    • original_filename — original file name

POST /v1/zcrm/customers/<c_id>/feed

Adds a text note to client timeline with an ability to attach files.

Address parameters

• c_id — client identification

Parameters

• content — note text content
• files — attached files array

Response

{
  "id": 37825,
  "type": "note",
  "content": "Call to client",
  "time": "2020-06-08 06:55:02",
  "user_id": 20,
  "user_name": "John Smith",
  "attached_files": [
    {
      "file_id": 576,
      "original_filename": "filename.doc"
    }
  ]
}

where:

• id — record identification
• type — record type. In this case is equal to:
  • note — text note
• content — note text content
• time — record time in format `YYYY-MM-DD hh:mm:ss`
• user_id — user identification, who created a record
• user_name — user name, who created a record
• attached_files — array of files attached to a note (if record type is a note). Each array element contains the following attributes:
  • file_id — file identification
  • original_filename — original file name

PUT /v1/zcrm/customers/<c_id>/feed/<i_id>

>Updates an existing text note by its ID.

Address parameters

• c_id — client identification
• i_id — text note identification

Parameters

• content — new note text

DELETE /v1/zcrm/customers/<c_id>/feed/<i_id>

Deletes a note in client timeline by its ID.

Address parameters

• c_id — client identification
• i_id — text note identification

GET /v1/zcrm/customers/<c_id>/employees

Restores client employees list by its ID.

Address parameters

• c_id — client identification

Response

{
  "totalCount": 5,
  "employees": [
    {
      "id": 23,
      "customer_id": 11,
      "name": "John Smith",
      "position": "manager",
      "position_title": "",
      "comment": "",
      "phones": [
        {
          "type": "work",
          "phone": "+44123456789"
        }
      ],
      "contacts": [
        {
          "type": "email_work",
          "value": "john@example.com"
        }
      ]
    }
  ]
}

where:

• totalCount — number of client’s employees
• employees — client’s employees array. Each array element contains the following attributes:
  • id — employee identification
  • customer_id — client identification to whom the employee is attached
  • name — employee name
  • position — employee position. Possible values:
    • ceo — CEO
    • director — director
    • manager — manager
    • sales_manager — sales manager
    • hr — HR
    • support — support
    • custom — custom
  • position_title — custom position title (for position = custom)
  • comment — employee description
  • phones — employee phone numbers array. Each number includes the following fields:
    • type — number type. Possible value:
      • work — work
      • personal — personal
    • phone — phone number value
  • contacts — employee contacts array. Each contact contains the following field:
    • type — contact type. Possible values:
      • email_work — work e-mail
      • email_personal — personal e-mail
      • skype
      • telegram
      • viber
      • whatsapp
    • value — contact value

GET /v1/zcrm/customers/<c_id>/employees/<e_id>

Restores client employee by its ID.

Address parameters

• c_id — client identification
• e_id — employee identification

Response

{
  "id": 23,
  "customer_id": 11,
  "name": "John Smith",
  "position": "manager",
  "position_title": "",
  "comment": "",
  "phones": [
    {
      "type": "work",
      "phone": "+44123456789"
    }
  ],
  "contacts": [
    {
      "type": "email_work",
      "value": "john@example.com"
    }
  ]
}

where:

• id — employee identification
• customer_id — client identification to whom the employee is attached
• name — employee name
• position — employee position. Possible values:
  • ceo — CEO
  • director — director
  • manager — manager
  • sales_manager —sales manager
  • hr — HR
  • support — support
  • custom — custom
• position_title — custom position title (for position = custom)
• comment — employee description
• phones — employee phone number array. Each number contains the following field:
  • type — number type. Position values:
    • work — work
    • personal — personal
  • phone — phone number value
• contacts — employee contacts array. Each contact contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value

POST /v1/zcrm/customers/<c_id>/employees

Creates and saves a new employee for a chosen client.

Address parameters

• c_id — client identification

Parameters

• employee — new employee information. Employee structure:

{
    "name": "John Smith",
    "position": "manager",
    "position_title": "",
    "comment": "",
    "phones": [
      {
        "type": "work",
        "phone": "+44123456789"
      }
    ],
    "contacts": [
      {
        "type": "email_work",
        "value": "john@example.com"
      }
    ]
  }

where:

• name — employee name
• position — employee position. Possible values:
  • ceo — CEO
  • director — director
  • manager — manager
  • sales_manager — sales manager
  • hr — HR
  • support — support
  • custom — custom
• position_title — custom position title (for position = custom)
• comment — employee description
• phones — employee phone number array. Each number contains the following field:
  • type — phone number. Possible values:
    • work — work
    • personal — personal
  • phone — phone number value
• contacts — employee contacts array. Each contact contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value

Response

{
  "id": 23
}

where:

• id — new employee identification

PUT /v1/zcrm/customers/<c_id>/employees/<e_id>

Updates an existing employee with an indicated ID.

Address parameters

• c_id — client identification
• e_id — employee identification

Parameters

• employee — new employee information. Structure:

{
    "name": "John Smith",
    "position": "manager",
    "position_title": "",
    "comment": "",
    "phones": [
      {
        "type": "work",
        "phone": "+44123456789"
      }
    ],
    "contacts": [
      {
        "type": "email_work",
        "value": "john@example.com"
      }
    ]
}

where:

• name — employee name
• position — employee position. Possible values:
  • ceo — CEO
  • director — director
  • manager — manager
  • sales_manager — sales manager
  • hr — HR
  • support — support
  • custom — custom
• position_title — custom position title (for position = custom)
• comment — employee description
• phones — employee phone number array. Each number contains the following field:
  • type — phone number. Possible values:
    • work — work
    • personal — personal
  • phone — phone number value
• contacts — employee contacts array. Each contact contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value

DELETE /v1/zcrm/customers/<c_id>/employees/<e_id>

Deletes an employee by ID.

Address parameters

• c_id — client identification
• e_id — employee identification

GET /v1/zcrm/events

Restores task list.

Parameters

• search (optional) - search bar. Search is carried out in combination by:
  
  • task name
  • task description
  • comments to completed tasks
• filter (optional) - task filter. Filter structure:
  

  {
      "responsible": 456,
      "createdBy": 456,
      "start": "2020-06-03 02:56:00",
      "end": "2020-06-12 02:56:00",
      "completed": 1
  }

  where:

  • responsible —responsible (user identification)
  • createdBy — created by (user identification)
  • start — display tasks starting after the specified time (in format `YYYY-MM-DD hh:mm:ss`)
  • end — display tasks ending before the specified time (in format `YYYY-MM-DD hh:mm:ss`)
  • completed — set in 1 to also display completed tasks
• sort (optional) - task sorting. Parameter structure:
  

  {
      "attr": "start",
      "desc": 0
  }

  where:

  • attr — sorting field. Valid value:
    • responsible — responsible user
    • title — task title
    • start — task beginning time
    • end — task ending time
  • desc — sorting order. Valid value:
    • 0 — ascending
    • 1 — descending

Response

{
  "totalCount": 4,
  "events": [
    {
      "id": 40,
      "type": "task",
      "title": "Call to GoodCompany",
      "description": "",
      "start": "2020-05-26 09:00:00",
      "end": "2020-05-26 12:30:00",
      "allDay": false,
      "created_by": 234,
      "responsible_user": 234,
      "phone": "",
      "call_done": 0,
      "completed": 0,
      "completed_comment": "",
      "members": [234, 235],
      "customers": [
        {
          "id": 3486,
          "name": "GoodCompany",
          "status": "company",
          "type": "client",
          "lead_source": "manual",
          "lead_status": "not_processed",
          "contact_type": "customer"
        }
      ]
    }
  ]
}

where

• totalCount — total number of tasks
• events — tasks array. Each task contains the following attributes:
  • id — task identification
  • type — task type. Possible values:
    • task — task
    • call — call
  • title — task title
  • description — task description (in format: Quill Delta: https://quilljs.com/docs/delta/)
  • start — task beginning date and time (in format `YYYY-MM-DD hh:mm:ss`)
  • end — task ending date and time (in format `YYYY-MM-DD hh:mm:ss`)
  • allDay — all-day task (`true` or `false`) — date is determined by parameter start
  • created_by — identification of the user who created the task
  • responsible_user — identification of the responsible user
  • phone — phone number for a call (if task type is call)
  • call_done — indicates if the call was made
  • completed — indicated of the task was marked as complete
  • completed_comment — comment to a completed task
  • members — task members array (only users’ identifications)
  • customers — array of clients and leads attached to the task. Each array element contains the following fields:
    • id — client/lead identification
    • name — client/lead name
    • status — client status. Possible values:
      • individual — personal user
      • company — company/business
    • type — client type. Possible values:
      • potential — potential client
      • client — client
      • reseller — reseller
      • partner — partner
    • lead_source — lead source. Possible values:
      • manual — manual
      • call_incoming — incoming call
      • call_outgoing — outgoing call
      • form — form
    • lead_status — lead status. Possible values:
      • not_processed — not processed
      • in_progress — in progress
      • finished — finished
    • contact_type — contact type. Possible values:
      • customer — client
      • lead — lead

GET /v1/zcrm/events/<event_id>

Restores a task by its ID.

Response

{
  "id": 40,
  "type": "task",
  "title": "Call to GoodCompany",
  "description": "",
  "start": "2020-05-26 09:00:00",
  "end": "2020-05-26 12:30:00",
  "allDay": false,
  "created_by": 234,
  "responsible_user": 234,
  "phone": "",
  "call_done": 0,
  "completed": 0,
  "completed_comment": "",
  "members": [234, 235],
  "customers": [
    {
      "id": 3486,
      "name": "GoodCompany",
      "status": "company",
      "type": "client",
      "lead_source": "manual",
      "lead_status": "not_processed",
      "contact_type": "customer"
    }
  ]
}

where

• id — task identification
• type — task type. Possible values:
  • task — task
  • call — call
• title — task title
• description — task description (in format Quill Delta: https://quilljs.com/docs/delta/)
• start — task starting date and time (in format `YYYY-MM-DD hh:mm:ss`)
• end — task ending date and time (in format `YYYY-MM-DD hh:mm:ss`)
• allDay — all-day task (`true` or `false`)
• created_by — identification of the user who created the task
• responsible_user — identification of the responsible user
• phone — phone number for the call (if task type is call)
• call_done — indicates if the call was made
• completed — indicated the task was completed
• completed_comment — comments to a completed task
• members — task members array (only user identifications)
• customers — array of clients and leads attached to the task. Each array element contains the following fields:
  • id — client/lead identification
  • name — client/lead name
  • status — client status. Possible values:
    • individual — personal user
    • company — company/business
  • type — client type. Possible values:
    • potential — potential client
    • client — client
    • reseller — reseller
    • partner — partner
  • lead_source — lead source. Possible value:
    • manual — manual
    • call_incoming — incoming call
    • call_outgoing — outgoing call
    • form — form
  • lead_status — lead status. Possible values:
    • not_processed — not processed
    • in_progress — in progress
    • finished — finished
  • contact_type — contact type. Possible values:
    • customer — client
    • lead — lead

POST /v1/zcrm/events

Created a new task with indicated information.

Parameters

• event — new task information. Structure:

{
    "type": "task",
    "title": "Call to GoodCompany",
    "description": "",
    "start": "2020-05-26 09:00:00",
    "end": "2020-05-26 12:30:00",
    "allDay": false,
    "responsible_user": 234,
    "phone": "",
    "members": [234, 235],
    "customers": [3486, 3487]
}

where

• type — task type. Valid values:
  • task — task
  • call — call
• title — task title
• description — task description (in format Quill Delta: https://quilljs.com/docs/delta/)
• start — task beginning date and time (in format `YYYY-MM-DD hh:mm:ss`)
• end — task ending date and time (in format `YYYY-MM-DD hh:mm:ss`)
• allDay — all-day task (`true` or `false`)
• responsible_user — responsible user identification
• phone — phone number for the call (if task type is call)
• members —task members array (only user identifications)
• customers — attached clients and leads array (only client and lead identification)

Response

{
  "id": 7216
}

where

• id — new task identification

PUT /v1/zcrm/events/<event_id>

Updates an existing task with indicated ID.

Parameters

• event — new task information. Structure:

{
    "title": "Call to GoodCompany",
    "description": "",
    "start": "2020-05-26 09:00:00",
    "end": "2020-05-26 12:30:00",
    "allDay": false,
    "created_by": 234,
    "responsible_user": 234,
    "phone": "",
    "members": [234, 235],
    "customers": [3486, 3487]
}

where

• title — task title
• description — task description (in format Quill Delta: https://quilljs.com/docs/delta/)
• start — task beginning date and time (in format `YYYY-MM-DD hh:mm:ss`)
• end — task ending date and time (in format `YYYY-MM-DD hh:mm:ss`)
• allDay — all-day task (`true` or `false`)
• responsible_user — responsible user identification
• phone — phone number for the call (if task type is call)
• members — task members array (only user identification)
• customers — attached client and lead array (only client and lead identification)

POST /v1/zcrm/events/<event_id>/close

Completes (closes) the task.

Parameters

• comment (optional) - comment

DELETE /v1/zcrm/events/<event_id>

Deleted a task by its ID.

No parameters

GET /v1/zcrm/leads

Restores lead list.

Parameters

• search (optional) - search bar. Search is carried out in combination by:
  
  • lead name
  • lead phone number
  • lead description
  • address and zip code
  • website
  • email address
  • messengers
• filter (optional) - lead filter. Filter structure:
  

  {
      "source": "call_incoming",
      "responsible": 32,
      "label": 12,
      "createdAfter": "2020-06-11 12:24:00",
      "createdBefore": "2020-06-26 12:24:00"
  }

where

• source — lead source. Possible values:
  • manual — manual
  • call_incoming — incoming call
  • call_outgoing — outgoing call
  • form — callback form
• responsible — responsible (user identification). The parameter also allows special values:
  • null — will return all leads assigned to someone
  • –1 — will return all raw leads
  • –2 — will return all leads (assigned and raw)
• label — label/tag (identification)
• createdAfter — display only leads created after the specified time (format: `YYYY-MM-DD hh:mm:ss`)
• createdBefore — display only leads created before the specified time (format: `YYYY-MM-DD hh:mm:ss`)

• sort (optional) - lead sorting. Parameter structure:
  

  {
      "attr": "name",
      "desc": 0
  }

  where

  • attr — sorting field. Possible values:
    • name — lead name
    • lead_source — lead source
    • lead_status — lead status
    • responsible_user_id — responsible user
    • lead_created_at — lead creation time
  • desc — sorting order. Possible values:
    • 0 — ascending
    • 1 — descending
• take (pagination) - how many leads to return (20 by default)
• skip (pagination) - how many leads to skip (0 by default)

Response

{
  "totalCount": 100,
  "uncategorizedCount": 10,
  "leads": [
    {
      "id": 3486,
      "name": "GoodCompany",
      "responsible_user_id": 234,
      "employees_count": "50",
      "comment": "",
      "country": "GB",
      "city": "London",
      "address": "",
      "zip": "",
      "website": "",
      "lead_status": "not_processed",
      "lead_source": "manual",
      "lead_created_at": "2020-04-28 05:47:47",
      "lead_created_by": 234,
      "phones": [
        {
          "type": "work",
          "phone": "+44123456789"
        }
      ],
      "contacts": [
        {
          "type": "email_work",
          "value": "good_company@example.com"
        }
      ],
      "labels": [
        {
          "id": 22,
          "label": "Best clients"
        }
      ]
    }
  ]
}

where

• totalCount — total number of found leads (including search bar and filter)
• uncategorizedCount — total number of raw leads (including search bar and filter)
• leads — lead array (including pagination). Each array element contains the following parameters:
  • id — lead identification
  • name — lead name
  • responsible_user_id — responsible (user identification)
  • employees_count — number of employees. Possible values:
    • 50 —less than 50
    • 50_250 — 50 – 250
    • 250_500 — 250 – 500
  • comment — lead description
  • country — lead county. Two-letter code (UK, US etc.)
  • city — lead city
  • address — lead address
  • zip — zip code
  • website — lead website
  • lead_status — lead status. Possible values:
    • not_processed — not processed
    • in_progress — in progress
    • finished — finished
  • lead_source — lead source. Possible values:
    • manual — manual
    • call_incoming — incoming call
    • call_outgoing — outgoing call
    • form —form
  • lead_created_at — lead creation date and time (in format `YYYY-MM-DD HH:mm:ss`)
  • lead_created_by — who created the lead (user identification)
  • phones — lead phone numbers array. Each number contains the following fields:
    • type — number type. Possible values:
      • work —work
      • personal — personal
    • phone — number value
  • contacts — lead contacts array. Each contact contains the following fields:
    • type — contact type. Possible values:
      • email_work — work e-mail
      • email_personal — personal e-mail
      • skype
      • telegram
      • viber
      • whatsapp
    • value — contact value
  • labels — array of leads assigned to a lead. Each label contains the following fields:
    • id — label identification
    • label — label value

GET /v1/zcrm/leads/<lead_id>

Restores lead by its ID.

Response

{
  "id": 3486,
  "name": "GoodCompany",
  "responsible_user_id": 234,
  "employees_count": "50",
  "comment": "",
  "country": "GB",
  "city": "London",
  "address": "",
  "zip": "",
  "website": "",
  "lead_status": "not_processed",
  "lead_source": "manual",
  "lead_created_at": "2020-04-28 05:47:47",
  "lead_created_by": 234,
  "phones": [
    {
      "type": "work",
      "phone": "+44123456789"
    }
  ],
  "contacts": [
    {
      "type": "email_work",
      "value": "good_company@example.com"
    }
  ],
  "labels": [
    {
      "id": 22,
      "label": "Best clients"
    }
  ],
  "custom_properties": [
    {
      "id": 12,
      "key": "loyalty",
      "title": "Loyalty",
      "value": "high"
    }
  ]
}

where

• id — lead identification
• name — lead name
• responsible_user_id — responsible (user identification)
• employees_count — number of employees. Possible values:
  • 50 — less than 50
  • 50_250 — 50 – 250
  • 250_500 — 250 – 500
• comment — lead description
• country — lead country. Two-letter code (UK, US etc.)
• city — lead city
• address — lead address
• zip — zip code
• website — lead website
• lead_status — lead status. Possible values:
  • not_processed — not processed
  • in_progress — in progress
  • finished —finished
• lead_source — lead source. Possible values:
  • manual — manual
  • call_incoming — incoming call
  • call_outgoing — outgoing call
  • form — form
• lead_created_at — lead creation date and time (in format `YYYY-MM-DD HH:mm:ss`)
• lead_created_by — who created the lead (user identification)
• phones — lead phone numbers array. Each number contains the following fields:
  • type — number type. Possible values:
    • work — work
    • personal — personal
  • phone — number value
• contacts — lead contacts array. Each contact contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value
• labels — array of labels assigned to a lead. Each label contains the following fields:
  • id — label identification
  • label — label value

POST /v1/zcrm/leads

Creates a new lead with indicated information.

Parameters

• convert — convert lead to client. Valid values:
  
  • 0 — don not convert, create a lead
  • 1 — create a client
  • 2 — poor (the action will be canceled – lead or client will not be created)
• lead — new lead information. Lead structure:
  

  {
      "name": "GoodCompany",
      "responsible_user_id": 234,
      "employees_count": "50",
      "comment": "",
      "country": "RU",
      "city": "Москва",
      "address": "",
      "zip": "",
      "website": "",
      "lead_source": "manual",
      "lead_status": "in_progress",
      "phones": [
        {
          "type": "work",
          "phone": "+44123456789"
        }
      ],
      "contacts": [
        {
          "type": "email_work",
          "value": "good_company@example.com"
        }
      ],
      "labels": [
        { "id": 22 },
        { "id": 23 }
    ],
      "custom_properties": [
      {
          "id": 12,
          "value": "high"
        }
      ]
  }

  where

  • name — lead name
  • responsible_user_id — responsible (user identification)
  • employees_count — number of employees. Valid values:
    • 50 — less than 50
    • 50_250 — 50 – 250
    • 250_500 — 250 – 500
  • comment — lead description
  • country — lead country. Two-letter code (UK, US etc.)
  • city — lead city
  • address — lead address
  • zip — lead zip code
  • website — lead website
  • lead_source — lead source. Valid values:
    • manual — manual
    • call_incoming — incoming call
    • call_outgoing — outgoing call
    • form —form
  • lead_status — lead status. Valid values:
    • not_processed — not processed
    • in_progress — in progress
    • finished — finished
  • phones — phone number array. Each number must contain the following fields:
    • type — number type. Possible values:
      • work — work
      • personal — personal
    • phone — number value
  • contacts — lead contacts array. Each contact must contain the following fields:
    • type — contact type. Possible values:
      • email_work — work e-mail
      • email_personal — personal e-mail
      • skype
      • telegram
      • viber
      • whatsapp
    • value — contact value
  • labels — array of labels assigned to the lead. Each element must contain:
    • id — existing label identification
    • custom_properties — additional features array. Each element must contain:
      • id — additional feature identification or:
      • key — additional feature unique name
      • value — additional feature value

Response

{
  "id": 123
}

where

• id — created lead identification

PUT /v1/zcrm/leads/<lead_id>

Updates an existing lead with an indicated ID.

Parameters

• convert — convert lead to client. Valid values:
  
  • 0 — do not convert
  • 1 — create a client
  • 2 — poor (delete lead)
• lead — new lead information. Lead structure:

{
    "name": "GoodCompany",
    "responsible_user_id": 234,
    "employees_count": "50",
    "comment": "",
    "country": "GB",
    "city": "London",
    "address": "",
    "zip": "",
    "website": "",
    "lead_source": "manual",
    "lead_status": "in_progress",
    "phones": [
      {
        "type": "work",
        "phone": "+44123456789"
      }
    ],
    "contacts": [
      {
        "type": "email_work",
        "value": "good_company@example.com"
      }
    ],
    "labels": [
      { "id": 22 },
      { "id": 23 }
  ],
    "custom_properties": [
    {
        "id": 12,
        "value": "high"
      }
    ]
}

where

• name — lead name
• responsible_user_id — responsible (user identification)
• employees_count — number of employees. Valid values:
  • 50 — less than 50
  • 50_250 — 50 – 250
  • 250_500 — 250 – 500
• comment — lead description
• country — lead country. Two-letter code (UK, US etc.)
• city — lead city
• address — lead address
• zip — lead zip code
• website — lead website
• lead_source — lead source. Valid value:
  • manual — manual
  • call_incoming — incoming call
  • call_outgoing — outgoing call
  • form — form
• lead_status — lead status. Valid values:
  • not_processed — not processed
  • in_progress — in progress
  • finished — finished
• phones — phone numbers array. Each number must contain the following fields:
  • type — number type. Possible values:
    • work — work
    • personal — personal
  • phone — number value
• contacts — lead contacts array. Each contact must contain the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value
• labels — array of labels assigned to a lead. Each element must contain:
  • id — existing label identification
• custom_properties — additional features array. Each element must contain:
  • id — additional features identification or:
  • key — additional features unique name
  • value — additional features value

DELETE /v1/zcrm/leads/<lead_id>

Deleted a lead by its ID.

No parameters

GET /v1/zcrm/users

Restores users list.

Response

{
  "totalCount": 2,
  "users": [
    {
      "id": 234,
      "email": "john_smith@example.com",
      "name": "John Smith",
      "group_id": 653,
      "is_superadmin": 1,
      "enabled": 1,
      "created_at": "2020-04-27 01:01:31",
      "avatar": 2457,
      "role": "",
      "status": "",
      "language": "en",
      "color": "220",
      "color_hex": "5678BD",
      "internal_number": "100",
      "timezone": "Europe/London",
      "first_day": 1,
      "device": "webphone",
      "phone_widget_location": "right",
      "phones": [
        {
          "phone": "+44123456789",
          "type": "work"
        }
      ],
      "contacts": [
        {
          "type": "email_work",
          "value": "smith@example.com"
        }
      ]
    }
  ]
}

where

• totalCount — total number of users
• users — user array. Each array element contains the following attributes:
  • id — user identification
  • email — user account e-mail
  • name — user name
  • group_id — user group identification
  • is_superadmin — indicates if the user is a super-adminitrator (1 or 0)
  • enabled — if the user is unblocked (1 or 0)
  • created_at — user creation date and time (in format `YYYY-MM-DD hh:mm:ss`)
  • avatar — user avatar (file identification)
  • role — user position
  • status — user status
  • language — user interface language. Possible values:
    • de — German
    • en — English
    • es — Spanish
    • pl — Polish
    • ru — Russian
    • ua — Ukranian
  • color — task color in ZCRM interface (only hue value — from 0 to 359)
  • color_hex —task color in ZCRM (hex-presentation)
  • internal_number — user PBX extension number
  • timezone — user timezone
  • first_day —indicates what week day is the beginning of the week:
    • 0 — Sunday
    • 1 — Monday
  • device — what is used for calls. Possible values:
    • webphone — webphone
    • softphone — third-party softphone
  • phone_widget_location — webphone widget location. Possible values:
    • left — display the widget on the left
    • right — display the widget on the right
  • phones — user phone numbers array. Each number contains the following fields:
    • phone — number value
    • type — number type. Possible values:
      • work — work
      • personal — personal
  • contacts — user contacts array. Each contact contains the following fields:
    • type — contact type. Possible values:
      • email_work — work e-mail
      • email_personal — personal e-mail
      • skype
      • telegram
      • viber
      • whatsapp
    • value — contact value

GET /v1/zcrm/users/<user_id>

Restores user by its ID.

Response

{
  "id": 234,
  "email": "john_smith@example.com",
  "name": "John Smith",
  "group_id": 653,
  "is_superadmin": 1,
  "enabled": 1,
  "created_at": "2020-04-27 01:01:31",
  "avatar": 2457,
  "role": "",
  "status": "",
  "language": "ru",
  "color": "220",
  "color_hex": "5678BD",
  "internal_number": "100",
  "timezone": "Europe/London",
  "first_day": 1,
  "device": "webphone",
  "phone_widget_location": "right",
  "phones": [
    {
      "phone": "+44123456789",
      "type": "work"
    }
  ],
  "contacts": [
    {
      "type": "email_work",
      "value": "smith@example.com"
    }
  ],
  "pending_email_change_request": false
}

where

• id — user identification
• email — user e-mail account
• name — user name
• group_id — user group identification
• is_superadmin — indicates if the user is a super-adminitrator (1 or 0)
• enabled — if the user is unblocked (1 or 0)
• created_at — user creation date and time (in format `YYYY-MM-DD hh:mm:ss`)
• avatar — user avatar (file identification)
• role — user position
• status — user status
• language — user interface language. Possible values:
  • de — German
  • en — English
  • es — Spanish
  • pl — Polish
  • ru — Russian
  • ua — Ukranian
• color — task color in ZCRM interface (only hue value — from 0 to 359)
• color_hex — task color in ZCRM (hex-presentation)
• internal_number — user PBX extension number
• timezone — user timezone
• first_day — what week day is the beginning of the week:
  • 0 — Sunday
  • 1 — Monday
• device — what is used for calls. Possible values:
  • webphone — webphone
  • softphone — third-party softphone
• phone_widget_location — webphone widget location. Possible values:
  • left — display the widget on the left
  • right — display the widget on the right
• phones — массив телефонных номеров пользователя. Каждый номер содержит следующие поля:
  • phone — значение номера
  • type — тип номера. Возможные значения:
    • work — рабочий
    • personal — личный
• contacts — user phone numbers array. Each number contains the following fields:
  • type — contact type. Possible values:
    • email_work — work e-mail
    • email_personal — personal e-mail
    • skype
    • telegram
    • viber
    • whatsapp
  • value — contact value
• pending_email_change_request —if account email change has been sent, but is not yet confirmed, this parameter will be set in true

GET /v1/zcrm/users/<user_id>/working-hours

Restores user work hours.

Response

{
  "schedulePeriod": 7,
  "scheduleWorkingHours": [
    {
      "time_start": "2020-06-15 09:00:00",
      "time_end": "2020-06-15 18:00:00"
    }
  ],
  "scheduleFixes": [
    {
      "index": 2,
      "repeat_index": 1,
      "time_start": "2020-06-24 09:00:00",
      "time_end": "2020-06-24 13:00:00",
      "deleted": 0
    }
  ],
  "customWorkingHours": [
    {
      "time_start": "2020-06-27 11:00:00",
      "time_end": "2020-06-27 15:00:00"
    }
  ]
}

where

• schedulePeriod — schedule frequency, *how often* is it repeated. For a regular week it’s 7 days, for day-in day-out it’s 2 days etc.
• scheduleWorkingHours — work schedule array. Each work schedule contains the following attributes:
  • time_start — beginning of work time in format `YYYY-MM-DD hh:mm:ss`
  • time_end — end of work time in format `YYYY-MM-DD hh:mm:ss`
• scheduleFixes — array of changes entered during working periods indicated in parameter scheduleWorkingHours. Each array element contains the following attributes:
  • index — element index in scheduleWorkingHours, meaning what working period was changed
  • repeat_index — schedule frequency index, in which the changes of future periods occur
  • time_start — new beginning of working time in format `YYYY-MM-DD hh:mm:ss`
  • time_end — new end of working time in format `YYYY-MM-DD hh:mm:ss`
  • deleted — if it equals 1, the working period is fully deleted
• customWorkingHours — array of custom, single working periods. Each working period contains the following attributes:
  • time_start — beginning of work time in format `YYYY-MM-DD hh:mm:ss`
  • time_end — end of work time in format `YYYY-MM-DD hh:mm:ss`

GET /v1/zcrm/users/groups

Restores groups and users rights in each of them.

Response

{
  "totalCount": 4,
  "groups": [
    {
      "id": 45,
      "type": "manager",
      "title": "",
      "permissions": {
        "customers_create": true,
        "customers_edit": true,
        "customers_delete": true,
        "customers_import_export": true,
        "customers_view_all": false,
        "calendar_other_users_access": false,
        "calls_other_users_access": false,
        "leads_view": false,
        "leads_edit": false,
        "leads_delete": false,
        "leads_import_export": false,
        "team_add": false,
        "team_edit": false
      }
    }
  ]
}

where

• totalCount — total number of groups
• groups — groups array. Each group contains the following attributes:
  
  • id — group identification
  • type — group type. Possible values:
    • admin — admins
    • manager — managers
    • chat_operator — operators
    • trainee — trainees
    • custom — custom
  • title — custom group title ( or type = custom)
  • permissions — group user rights. Admins have a full access, that is why for admins this subject will be empty. Other groups contain the following attributes (each of them can be equal to `true` or `false`):
    • customers_create — client creation allowed
    • customers_edit — client editing allowed
    • customers_delete — client deletion allowed
    • customers_import_export — client import and export allowed
    • customers_view_all — all client viewing is allowed, including the ones assigned by other users
    • calendar_other_users_access — other users’ task viewing allowed
    • calls_other_users_access — access to other users’ calls is allowed
    • leads_view — only viewing of other users’ leads is allowed
    • leads_edit — other users’ lead editing is allowed
    • leads_delete — other users’ lead deletion is allowed
    • leads_import_export — lead export and import are allowed
    • team_add — adding and inviting other users to the team is allowed
    • team_edit — user editing is allowed

GET /v1/zcrm/calls

Restores call list.

Parameters

• search (optional) - search bar. Search is carried out in combination by:
  
  • phone numbers
  • contact names (clients, employees, leads or users)
• filter (optional) - call filter. Filter structure:
  

  {
      "user": 23,
      "type": "incoming",
      "status": "answer",
      "dateFrom": "2020-06-03 14:56:00",
      "dateTo": "2020-06-26 14:56:00"
  }

  where

  • user — user (identification)
  • type — call type. Valid values:
    • incoming — incoming call
    • outgoing — outgoing call
  • status — call status. Valid values:
    • answer — successful call
    • noanswer — no answer
    • cancel — canceled calls
    • busy — busy
    • failed — failed call
  • dateFrom — display only calls made after specified time (format: `YYYY-MM-DD hh:mm:ss`)
  • dateTo — display only calls made before specified time (format: `YYYY-MM-DD hh:mm:ss`)

• sort (optional) - call sorting. Parameter structure:
  

    {
      "attr": "time",
      "desc": 0
    }

  where

  • attr — sorting field. Valid values:
    • phone — phone number
    • status — call status
    • duration — call duration
    • time — call time
  • desc — sorting direction. Valid values:
    • 0 — ascending
    • 1 — decending
• take (pagination) - how many calls to return (20 by default)
• skip (pagination) - how many calls to skip (0 by default)

Response

{
  "totalCount": 233,
  "calls": [
    {
      "id": 127,
      "type": "outgoing",
      "status": "answer",
      "phone": "+44123456789",
      "user_id": 179,
      "time": "2019-07-31 17:58:40",
      "duration": 9,
      "pbx_call_id": "out_807ghh1h7f09fa7a188dbf8a6998b1c9ghg4ij06",
      "record": 1,
      "record_url_till": "2020-07-24 20:08:10",
      "contact_type": "customer",
      "contact_name": "GoodCompany",
      "contact_customer_id": 3486,
      "contact_employee_id": null,
      "employee_customer_id": null,
      "contact_user_id": null,
      "is_lead": 1,
      "record_urls": [
        {
          "url": "https://api.zadarma.com/v1/pbx/record/download/[...]/[...]/[...].mp3"
        }
      ]
    }
  ]
}

where

• totalCount — total number of calls (including search bar and filter)
• calls — call array (including pagination). Each array element contains the following parameters:
  
  • id — call identification
  • type — call type. Possible values:
    • incoming — incoming call
    • outgoing — outgoing call
  • status — call status. Possible values:
    • answer — successful call
    • noanswer — no answer
    • cancel — canceled
    • busy — busy
    • failed — failed call
  • phone — phone number
  • user_id — user, who initiated or accepted the call
  • time — call time in format `YYYY-MM-DD hh:mm:ss`
  • duration — call duration in seconds
  • pbx_call_id — call identification in Zadarma PBX
  • record — if call recording enabled
  • record_url_till — time, until when call recording link will be active
  • contact_type — contact type. Possible values:
    • customer — client or lead (see parameter is_lead)
    • employee — client employee
    • user — user
  • contact_name — contact name
  • contact_customer_id — client or lead identification (if the call is related to a client)
  • contact_employee_id — employee identification (if the call is related to an employee)
  • employee_customer_id — parent entity identification (if the call is related to an employee)
  • contact_user_id — user identification (if the call is related to a user)
  • is_lead — shows if the call is related to a lead
  • record_urls — call recordings array (can be missing, as has to be specifically requested). Each array element is an object that contains the following field:
    • url — link to the call recording

GET /v1/zcrm/contacts

Restores the whole list of contacts (clients, employees, leads, users) with phone numbers.

Parameters

• search (optional) - search bar. Search is carried out in combination by:
  
  • names and phone numbers of clients, leads, employees and users
  • users PBX extension number
• take (pagination) - how many contacts to return (20 by default)
• skip (pagination) - how many contacts to skip (0 by default)

Response

{
  "totalCount": 128,
  "contacts": [
    {
      "contact_type": "customer",
      // clients attributes...
    },
    {
      "contact_type": "employee",
      // employee attributes...
    },
    {
      "contact_type": "lead",
      // leads attributes...
    },
    {
      "contact_type": "user",
      // users attributes...
    }
  ]
}

where

• totalCount — total contact number (including search bar)
• contacts — contact array. Each of the contacts depending on its type (client, employee, lead, user) will have its own set of attributes.
  

  Clients

  {
      "contact_type": "customer",
      "id": 3486,
      "name": "GoodCompany",
      "status": "company",
      "type": "client",
      "phone": {
        "phone": "+44123456789",
        "type": "work"
      },
      "responsible": {
        "id": 234,
        "name": "John Smith",
        "ext_num": "100"
      }
  }

  where

  li>contact_type — contact type:
  • customer —client
  • id — client identification
  • name — client name
  • status — client status. Possible values:
    • individual — personal user
    • company — company/business
  • type — client type. Possible values:
    • potential — potential client
    • client — client
    • reseller — reseller
    • partner — partner
  • phone — phone number. Contains the following fields:
    • phone — the number itself
    • type — number type. Possible values:
      • work — work
      • personal — personal
  • responsible — responsible user. Contains the following field:
    • id — user identification
    • name — user name
    • ext_num — user PBX extension number

  Client's employee

  {
          "contact_type": "employee",
          "id": 8,
          "name": "John Smith",
          "phone": {
            "phone": "+44123456789",
            "type": "work"
          },
          "position": {
            "position": "manager",
            "title": ""
          },
          "customer": {
            "id": 3486,
            "name": "GoodCompany"
          },
          "responsible": {
            "id": 234,
            "name": "John Smith",
            "ext_num": "100"
          }
  }

  where

  • contact_type — contact type:
    • employee — employee
  • id — employee identification
  • name — employee name
  • phone — phone number. Contains the following fields:
    • phone — the number itself
    • type — number type. Possible values:
      • work — work
      • personal — personal
  • position — employee position. Contains the following dields:
    • position — position value. Possible values:
      • ceo — CEO
      • director — director
      • manager — manager
      • sales_manager — sales manager
      • hr — HR
      • support — support
      • custom — custom
    title — custom position title (for position = custom)
  • customer — client to whom the employee is attached. Contains the following fields:
    • id — client identification
    • name — client name
    • responsible — user responsible for parent entity client. Contains the following fields:
      • id — user identification
      • name — user name
      • ext_num — user PBX extension number

  Lead

  {
  "contact_type": "lead",
  "id": 3486,
  "name": "GoodCompany",
  "phone": {
    "phone": "+44123456789",
    "type": "work"
  },
  "responsible": {
    "id": 234,
    "name": "John Smith",
    "ext_num": "100"
  }
  }

  where

  • contact_type — contact type:
    • lead — lead
  • id — lead identification
  • name — lead name
  • phone — phone number. Contains the following fields:
    • phone — the number itself
    • type — number type. Possible values:
      • work — work
      • personal — personal
  • responsible — responsible user. Contains the following fields:
    • id — user identification
    • name — user name
    • ext_num — user PBX extension number

  User

  {
      "contact_type": "user",
      "id": 234,
      "name": "John Smith",
      "avatar": 2457,
      "role": "",
      "status": "",
      "phone": {
        "phone": "100",
        "type": "internal"
      },
      "group": {
        "type": "admin",
        "title": ""
      }
    }

  where

  • contact_type — contact type:
    • user — user
  • id — user identification
  • name — user name
  • avatar — user avatar (file identification)
  • role — user role
  • status — user status
  • phone — phone number. Contains the following fields:
    • phone — the number itself
    • type — number type. Possible values:
      • work — work
      • personal — personal
      • internal — PBX extension number
  • group — user group. Contains the following fields:
    • type — group type. Possible values:
      • admin — admins
      • manager — managers
      • chat_operator — operators
      • trainee — trainees
      • custom — custom
    • title — custom group title (for type = custom)

GET /v1/zcrm/contacts/identify

Identifies contact (client, employee, lead, user) by the phone number.

Parameters

• phone — phone number

Response

Client

{
  "contact_type": "customer",
  "id": 3486,
  "name": "GoodCompany",
  "status": "company",
  "type": "client",
  "phone": {
    "phone": "+44123456789",
    "type": "work"
  },
  "responsible": {
    "id": 234,
    "name": "Jim Beam",
    "ext_num": "100"
  }
}

where

• contact_type — contact type:
  • customer — client
• id — client identification
• name — client name
• status — client status. Possible values:
  • individual — personal user
  • company — company/business
• type — client type. Possible values:
  • potential — potential client
  • client — client
  • reseller — reseller
  • partner — partner
• phone — phone number. Contains the following fields:
  • phone — the number itself
  • type — number type. Possible values:
    • work — work
    • personal — personal
• responsible — responsible user. Contains the following fields:
  • id — user identification
  • name — user name
  • ext_num — user PBX extension number

Client's employee

{
  "contact_type": "employee",
  "id": 8,
  "name": "John Smith",
  "phone": {
    "phone": "+44123456789",
    "type": "work"
  },
  "position": {
    "position": "manager",
    "title": ""
  },
  "customer": {
    "id": 3486,
    "name": "GoodCompany"
  },
  "responsible": {
    "id": 234,
    "name": "Jim Beam",
    "ext_num": "100"
  }
}

where

• contact_type — contact type:
  • employee — employee
• id — employee identification
• name — employee name
• phone — phone number. Contains the following fields:
  • phone — the number itself
  • type — number type. Possible values:
    • work — work
    • personal — personal
• position — employee position. Contains the following fields:
  • position — position. Possible values:
    • ceo — CEO
    • director — director
    • manager — manager
    • sales_manager — sales manager
    • hr — HR
    • support — support
    • custom — custom
  • title — custom position title (for position = custom)
• customer — client, to whom the employee is attached. Contains the following fields:
  • id — client identification
  • name — client name
• responsible — user responsible for the parent entity. Contains the following fields:
  • id — user identification
  • name — user name
  • ext_num — user PBX extension number

Lead

{
  "contact_type": "lead",
  "id": 3486,
  "name": "GoodCompany",
  "phone": {
    "phone": "+44123456789",
    "type": "work"
  },
  "responsible": {
    "id": 234,
    "name": "Jim Beam",
    "ext_num": "100"
  }
}

where

• contact_type — contact type:
  • lead — lead
• id — lead identification
• name — lead name
• phone — phone number. Contains the following fields:
  • phone — the number itself
  • type — number type. Possible values:
    • work — work
    • personal — personal
• responsible — responsible user. Contains the following fields:
  • id — user identification
  • name — user name
  • ext_num — user PBX extension number

User

{
  "contact_type": "user",
  "id": 234,
  "name": "John Smith",
  "avatar": 2457,
  "role": "",
  "status": "",
  "phone": {
    "phone": "100",
    "type": "internal"
  },
  "group": {
    "type": "admin",
    "title": ""
  }
}

where

• contact_type — contact type:
  • user — user
• id — user identification
• name — user name
• avatar — user avatar (file identification)
• role — user role
• status — user status
• phone — phone number. Contains the following fields:
  • phone — the number itself
  • type — number type. Possible values:
    • work — work
    • personal — personal
    • internal — PBX extension number
• group — user group. Contains the following fields:
  • type — group type. Possible values:
    • admin — admins
    • manager — managers
    • chat_operator — operators
    • trainee — trainees
    • custom — custom
  • title — custom group title (for type = custom)

GET /v1/zcrm/files/<file_id>

Gives files by its ID.

No parameters