LiveZilla Live Chat
EN  DE Please sign in or register Hi
A fabulous tool for keeping in touch with my Team members when we need to work together. As a business...
Adam
Show all reviews


LiveZilla API V2




TicketEditor
TicketEditor Object Format
TicketEditor is represented as JSON objects having the following keys:


JSON Key Type Required Read only Comment Example
EditorstringYesNoEditor (=Operator) IDjohn_doe
StatusintNoNo
Ticket Status

[0] = Open
[1] = In Progress
[2] = Closed
[3] = Deleted
Read more
SubStatusstringNoNoTicket Sub-StatusSub-Status Name, added in LiveZilla 6.1.0.0
IdstringYesNoTicket ID11123
GroupIdstringYesNoGroup Id, Operator must a member of this Groupgroupid1


TicketEditor Functions


Assign Ticket Editor
Function
As of version 5.2.5.0


POST /api/v2/api.php p_ticketeditor_assign=1


Filters


Name POST Key Type Required Comment Example  


CURL Example


curl {yourdomain}{livezilla_folder}/api/v2/api.php
-d {authenthication}
-d p_ticketeditor_assign=1
-d p_data={ "TicketEditor": { "GroupId": "groupid1", "SubStatus": "Sub-Status Name, added in LiveZilla 6.1.0.0<\/i>", "Id": "11123", "Editor": "john_doe", "Status": "0" } } -X POST

Response


200 Ok: {
    "TicketEditor": {
        "GroupId": "groupid1",
        "SubStatus": "Sub-Status Name, added in LiveZilla 6.1.0.0<\/i>",
        "Id": "11123",
        "Editor": "john_doe",
        "Status": "0"
    }
}

Error Codes


                            403 Forbidden: Invalid or no user authentication data sent (see General API Authentication)
400 Bad Data: Invalid or missing POST parameters (see required fields/filters and data types)
                        





Something missing?


If you find anything missing please let us know and we will add the missing structures right away. Thanks.